Jump to content

Search the Community

Showing results for tags 'feedback'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • BOHEMIA INTERACTIVE
    • BOHEMIA INTERACTIVE - NEWS
    • BOHEMIA INTERACTIVE - JOBS
    • BOHEMIA INTERACTIVE - GENERAL
  • FEATURED GAMES
    • ARMA 3
    • DAYZ
    • TAKE ON MARS
    • ARMA 2
    • ARGO
    • YLANDS
  • MOBILE GAMES
    • ARMA MOBILE OPS
    • MINIDAYZ
    • ARMA TACTICS
    • ARMA 2 FIRING RANGE
  • BI MILITARY GAMES FORUMS
  • BOHEMIA INCUBATOR
  • OTHER BOHEMIA GAMES
    • TAKE ON HELICOPTERS
    • CARRIER COMMAND: GAEA MISSION
    • ARMA: ARMED ASSAULT / COMBAT OPERATIONS
    • ARMA: COLD WAR ASSAULT / OPERATION FLASHPOINT
    • IRON FRONT: LIBERATION 1944
    • BACK CATALOGUE
  • OFFTOPIC
    • OFFTOPIC
  • ArmA Toolmakers's Releases
  • ArmA Toolmakers's General
  • Die Hard OFP Lovers' Club's Topics

XBOX Live


PlayStation PSN


Origin


PlayFire


SoundCloud


Pinterest


Reddit


Twitch.Tv


Ustream.Tv


Duxter


Instagram


Location


Interests


Interests


Occupation

Found 73 results

  1. Sometimes it's useful to discuss updates to the Steam Development branch in one centralized place. Let's use this thread for that. The changelog thread can stay clean and do its thing. It mainly serves for our team to rapidly see if a daily update is very broken or very epic :ph34r: Actual issue reporting should still happen via the Feedback Tracker of course. Thank you!
  2. The audio changes which delayed Development branch updates are now partly published. As with most of these large tasks, this is ongoing work and so the current state is not considered final (in some places it may be worse for a little while). Effectively the core foundations are in place and now each individual asset needs tuning and fixing. We feel it will improve the soundscape in the final game :622: Senior audio team member Ondřej Matějka goes over the details:
  3. Please let us know your thoughts on the Laws of War DLC assets (vehicles, weapons, character gear, props, etc.). Find out more about the asset production process in our OPREP on this topic. If you discover concrete issues, the most effective reporting method for us is Feedback Tracker. How do I access the assets? Main Menu: Shift + P In the DLC Content Browser, select Laws of War and explore its contents. Some assets have a TRY button that will open the asset in ... Main Menu: TUTORIALS > VIRTUAL ARSENAL (For vehicles, switch to the Garage mode at the top of the screen) Each asset category shows the appropriate DLC / mod icons behind each asset for easy identification. Use Sort by mod to make it even easier to find them. Note: in this mode you should be able to preview the assets without DLC ownership. Main Menu: EDITOR In the Asset Browser on the right, all assets are marked by the DLC / mod icon. Use Filter by mods option and select Arma 3 Laws of War. And you'll of course encounter the assets during gameplay! What assets are available?
  4. Please use this thread for discussion specific to the Release Candidate (RC) branch on Steam, when it's available in the weeks leading up to a release. The preferred method of reporting issues in that build is the Feedback Tracker. Thanks!
  5. Forums Upgrade

    Hello everyone, As you may have noticed, the forums have now been upgraded. Please use this thread to provide any feedback you might have. Best regards, BohemiaBeck
  6. NOTE: 1.74. PROF/PERF up! you don't need need new client on PERF/PROF server ! there is branch on steam you may use, but beware that sometimes data on my dropbox're newer due to manual build e.g. on weekend: Servers (down, up only if needed): PERF = STABLE branch compatible, no debug layer, no #captureFrame nor diag_captureFrame PROF = STABLE branch compatible, with debug layer, with #captureFrame / diag_captureFrame possible server fps increases and clients may experience higher fps too downloads
  7. Hi everyone, After more than four years of post-release development, the Arma 3 team is gradually moving onto new projects here at Bohemia Interactive. This includes the development of new games, as well as the development of the technology and tools that will power our future projects. Of course, we've not yet reached the final destination on the current Arma 3 roadmap, and with Tac-Ops and Tanks DLC on the way, there's still a lot to look forward to! Beyond that, as we'll be investing our resources into the longer-term future, it means that Arma 3 Tanks will most likely be our final, official, DLC release. Of course, we'll still be supporting the Arma 3 platform with updates afterwards. However, these should not involve major changes to the game's core architecture, which also makes it less likely for such updates to cause compatibility issues, and helps us to ensure a more stable platform overall. Regardless, thanks to our dedicated community, we're convinced that Arma 3 will remain active and relevant for many more years. Yet to help Arma 3 continue its life as a constantly evolving platform, there's one other idea that we wish to pursue. Namely, we'd like to work with external development teams, including the splendid developers in our community, to publish their Arma 3 projects as third-party premium DLC on Steam. As most of you probably already know, Arma 3 Jets DLC was the first opportunity for us to become familiar with third-party development partnerships. This DLC was developed together with BRAVO ZERO ONE STUDIOS (B01) - an external team led by Make Arma Not War winner Joshua "Saul" Carpenter. To put it simply, B01 developed the premium assets like the new jets and carrier, while our own development team took care of the related free platform features such as the sensor overhaul. It was a very challenging, but also satisfying and successful project. And even though we don't have the resources to directly support the development of any future third-party DLC (unlike the more cross-collaborative approach to Jets DLC), the overall experience has made us confident about extending this opportunity to other external developers. Furthermore, this opportunity also connects with our belief that quality content creators, including the talented developers in our community, deserve a financial reward for their hard work - and facilitating this would eventually lead to many benefits for everyone. At the same time, we're also very keen to preserve everything that makes community content and modding such a beloved component of our series. For this reason, let us already point out a few things: We'll be looking to select and publish new projects, but also existing projects that would be able to scale up in quality/quantity as a result of being published as a premium DLC. However, we'll always insist that any existing free Arma 3 addons and mods remain free. In other words, third-party DLC we publish should never replace something which was previously free. Different from Arma 3's official DLC so far, this new third-party premium DLC would always be an optional installation. This means you only download the DLC data after you've purchased the third-party DLC pack - and so if you didn't purchase and install the additional content, you wouldn't see it listed in Arma 3's main menu or in the Editor's content browser. As mentioned earlier, we'll not be able to offer development support for third-party DLC. However, we will provide guidelines on technical and quality requirements, assist with the Quality Assurance process, help with promotion and deliver the tools for mastering. Lastly, we know from experience how difficult it can be to bring a project to completion. With that in mind, we currently anticipate that probably only a few third-party premium DLC packs will get published each year. Our intention is to ensure a steady flow of exciting new Arma 3 content over the next few years, while also making sure not to clutter the game with an excessive amount of premium DLC. For now, we're mostly looking to get the ball rolling by inviting those who are interested in a collaboration to send us their DLC proposal. To do so, please send us your pitch (which should already include a working in-game prototype delivered as an Arma 3 mod) to businessdevelopment@bistudio.com. After we've evaluated your concept and if we see potential, we can start discussing the details of the agreement, the development schedule, and anything else that might be relevant to your project. All in all, we know you'll have many more questions, and quite honestly, we might not have all the answers just yet. We're currently in the process of formulating the basic guidelines, and forming the team of people who will be guiding the entire process. We'll probably also be making some mistakes and all be learning as we go. However, in the end, our ambition is straightforward and clear: to establish a third-party publishing framework which benefits our content creators, our players, and our longer-term future. In the meantime, if you have any questions, suggestions, or concerns, we welcome you to share them with us. Thank you for your interest - we'll keep you informed as things progress!
  8. From the outset the Laws of War DLC was going to focus on assets and playable content. However, there was room to enhance a few existing features relevant to the theme. A bunch of modest improvements to cluster munitions have been scattered over the past few updates (free for all players of course). Let's discuss them in this thread, and as always, please post concrete issues to Feedback Tracker. Note: expanded Community Wiki documentation is forthcoming. Most new properties are already described: https://community.bistudio.com/wiki/CfgAmmo_Config_Reference https://community.bistudio.com/wiki/Arma_3_Weapon_Config_Guidelines#Ammo_changes_on_fly_and_on_hit What changes does this cover? Added: Cluster Bombs (3 factions - see Pylon settings of aircraft) Previously only artillery cluster munitions were supported. Added: Unexploded Ordnance (3 factions x 4 triggers) Trigger types: Common: basically functions as a regular 'mine' Delayed: detonates a while after 'triggering' Tough: takes a lot of manipulation before detonating Sensitive: BOOM (even animals will set these off) These can be placed in Eden Editor, but are also randomly left behind after deploying various types of cluster munitions. The CAS module now features Bomb Strikes. Added: APERS Mine Dispenser* This means engine support for a mine that basically detonates like a sub-munition. Deployed mines can now have a randomized rotation. Various new SFX / VFX were added, as well as camera shake. The engine now supports control over sub-munition speed and ammo type randomization. * Restrictions apply for those who don’t own Arma 3 Laws of War DLC.
  9. Feedback Thread

    And nice to see Bohemia dedicate some resources towards testing new ideas and experimenting in coordination with the community in such a way. Will definately give it a go! Good luck with it!
  10. Hey everyone, we have released a first iteration of the Linux Dedicated Server as reported in SITREP #38. It's still a little bit experimental so we would very much appreciate your feedback and experience running it. Please report any bugs to our Feedback tracker (use the fields Platform, OS and OS Version to describe you distro as best as you can) while general feedback should go directly into this thread. There are some known issues so be aware of them when you run the server: Also note that java version 7 is required to run the server (even though it's disabled in-game) so you will have to set path to 'libjvm.so' correctly for your distro. Example usage on my debian: LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/jvm/java-7-openjdk-i386/jre/lib/i386/jamvm ./arma3server -netlog -config=Arma3_Server.cfg Enjoy!
  11. Mines (specifically detection) are another existing feature that we've had a chance to make a few improvements to with Laws of War DLC (as a platform update for all). Most of these changes have already been on Dev-Branch for a while and we've read your feedback so far. We'll divulge more of our goals and details over the next weeks in the form of OPREPs for example. Note that we've wanted to preserve backward-compatibility as much as possible, limiting some more drastic changes. A clear example is the 15 meter detection range. Sure, we could decrease it, but it would potentially unbalance any existing scenario with mines. Note: expanded Community Wiki documentation is in progress. Specific issues go to the Feedback Tracker as per usual. What changes does this cover? Most characters are now less adept at automatic visual identification of mines. You will need to manually T-reveal them in more cases (also depending on difficulty options). Note that in order to disarm mines, you need to have revealed them. Many other factors influence visual identification: night-time, being in a vehicle, hidden in vegetation, etc. The Mine Detector has the same 15 meter range as it always had, but is slightly less 'magical' now. An Info Panel is used to show the approximate location around you ([ or ] by default). It pings off nearby detected mines, but does not yet reveal their type (potentially offset cloud symbol). Audio cues reveal the direction and distance of the nearest unrevealed mine (also without the panel open). Vehicles can have their own Mine Detector with custom range and Info Panel (see the Demining Drone). Most explosives should receive their own placement / deactivation SFX (WIP). Many explosion SFX were tweaked. The Radio Protocol message that is triggered when a mine is discovered has 'spam control', so it's not repeated too often in a large field. disableAI "MINEDETECTION" can disable an AI's mine detection abilities.
  12. I've very nice news about headless client (HC) which is variant of dedicated client for server use we will be rolling out soon (days) new test version for both linux and windows - no more steamclient nor steam account with game ownership needed for HC - HC needs only steam dedicated server binary and set of commandline params - auto-connection recognize & detection of HC by server (server needs some config to allow that) - multiple HC per server are supported - HC can be primary used to offload AI work and secondary for some script jobs - logic for mission & scripting operations with HC introduced - HC are autoassigned to slots - HC are not visible to players - HC are visible to admins - HC isn't counted against playercount in server list - BattlEye supported (1.36 RC2 released 28.11.2014 18:00 CET) today's DEV: •Added: Enable new headless client implementation - see https://community.bistudio.com/wiki/Arma_3_Headless_Client for more details note: known limitation, none (except some AI bugs, need repro/confirm) note: what needs to be somewhat tested/determined/improved/changed is disconnect & reconnect of HC and all related to that post bugs, feedback and ideas below
  13. Leaflets are a scripted feature meant for use in playable content most of all (Laws of War DLC). There is some Sandbox compatibility, but since they are not fully engine-driven, they are also limited in some areas. For this reason they are not by default added to the Utility Drone (but can be added as special 'weapon' via pylon settings or scripting). Notes: Find a start of documentation on the Community Wiki. We've extended the feature to allow for full-screen inspection of the info stands (Faction Showcase IDAP e.g.). We'd prefer specific issue reports on the Feedback Tracker.
  14. ARMA needs a way for multiple players to view a UAVs live feed at once Currently doing research on how multiple players can connect to a UAVs turret view at once . This will be important for a assault team so each member can have eyes on the battlefield from the air using the AV camera. Does anyone know of a way or even a mod to address this gap in drone functionality? Right now, only 1 player can cannot to a UAVs view at a time. Can this feature be added in a patch please?
  15. UAVs: Feedback and wishes

    Hello everyone! As you probably know, there is a new UAV (Unmanned Autonomous Vehicle) system in Arma 3. This system should be more stable and robust than the old version presented in Arma 2. We believe that this change was a big step forward from Arma 2, but we also know that there are still some sharp edges in this feature. I would like to ask you for constructive feedback on current UAV system in Arma 3. Please try to explain why do you think that specific part of this system should be changed. We would appreciate even your ideal solution for any issue. You can talk about issues, solutions and your wishes as well. But as usual, try to be polite and don't go off-topic. Our main interest is the UAV system itself and its features. Of course, we would like to have more great UAV models in the game too, but that is not the point of this thread. I can't promise anything specific in the matter of UAVs right now. But I am going to read all your posts here and I hope we will be able to fix at least some weak spots in the UAV system. Thank you for your feedback!
  16. Video of problem: https://youtu.be/sdLyEm3NNRM Feedback tracker: https://feedback.bistudio.com/T125385 Hello! I've been using kbTell for some time now with solid success, however I recently noticed a bug. I'm actually not certain if this bug has always been present, or if I am just now noticing it. The reason for this post is to make sure it isn't my usage that's creating the issues. I am going to throw this into the feedback tracker as well. To sum up the video above, when kbTell is used on units that are not local to the person observing the conversation, only one person will speak at a time. So if player A is next to Bob and Bill, and Bob is supposed to talk at the same time Bill is, Bob will need to wait until Bill is done speaking, but Bob will lip sync on time. Now you might think this isn't a bug, in that they are having a conversation. The problem will be if Bob is miles away from Bill, talking about two different topics, Bill would still not say a darn thing until Bob is done, or vice versa. Now, if the units speaking are local to the observer, there is no issue. They will speak over each other if required. The video does a better job, showing both scenarios, so please take a gander if you have time. Here is the code used in the video: In game script: Ermy linkItem "ItemRadio"; Carl linkItem "ItemRadio"; Ermy kbAddTopic ["testTopic", "sentenceDB.bikb", "", ""]; Carl kbAddTopic ["testTopic", "sentenceDB.bikb", "", ""]; [] spawn {Carl kbTell [Carl, "testTopic", "Carl1B", ["",{},"",[""]], false]; sleep 0.5;Ermy kbTell [Ermy, "testTopic", "ErmyHelpPlane", ["",{},"",[""]], false];}; SentenceDB.bikb (located in the missions root) class Sentences { class ErmyHelpPlane { text = ""; speech[] = {"\BND\sound\Ermy\ErmyHelpPlane.ogg"}; variant = ""; variantText = ""; class Arguments {}; }; class Carl1B { text = ""; speech[] = {"\BND\sound\Missions\G01\Carl1B.ogg"}; variant = ""; variantText = ""; class Arguments {}; }; };
  17. Hi there, direct your feedback on the official Arma 3 Launcher here. This is (non-exclusively) related to the Launcher being the default way to launch the game starting from Thursday 26/03/15. Thanks :) Reminder: bugs still belong to Feedback Tracker in the Launcher category.
  18. Hi guys, A recent development branch update introduced, among the other things, new recoil mechanics. It should significantly improve the unique feeling of every particular weapon when firing. We put a great emphasis on the specific aspects of each weapon in particular to bring you the most authentic shooting experience we could get from mouse and keyboard. As always, every civilized and constructive feedback is indeed very important to us and so we would like to encourage you to discuss your opinions, feelings, expectation and experience with the feature itself and real weapon behavior as well for comparison. We will carefully monitor and process all your feedback to make sure that the feature is properly tuned and optimized for the release of Marksmen DLC. Thanks in advance, and see you at the shooting range.
  19. For the Arma 3 Alpha we have decided to make use of our own Feedback Tracker (FT - opened with the release on March 5th). Some of you will wonder why we do not use the DevHeaven Community Issue Tracker, so I will try to explain our rationale in this post. First of all, let me thank the people involved in running CIT, such as Sickboy, kju and the rest of its admin staff! Big thanks as well to those who took the time to report issues, work on good repro methods and validating fixes. This has especially helped with the ongoing development of the Operation Arrowhead beta patches. It's good to have a dedicated place to track issues, rather than to contain it all within the forums. That leaves these forums to be a place of discussion and community collaboration. For the Arma 3 Alpha we however wished things from the tracking platform that CIT did not currently do. I have no doubt its creators could eventually implement some of what we needed, but we had to get it up and running very quickly. Most of it was about direct administration control and connections to our own web services. In our vision for Arma 3, the consistent and complete package is important. We feel the Feedback Tracker is part of that, and so it should feel as close as possible to the rest of the websites and the game. If we decide to make a subtle change quickly (e.g. an artwork or disclaimer text), we need to be able to immediately get it done via our own web team. We are also expecting an influx of people who have no experience with CIT or our community at all. We need a platform those people can easily find and use. They should not be confused about whether the platform is official or not. In the end though, no matter what platform is used, the goal is for us to cooperate with you: developers and the community. We'd like to ask you to help us to do that. By reporting issues to us in a good way, we can do our best to correct them. By voting you let us know which issues are of key importance to you. On our end we are getting our pipelines ready to be able to more frequently update the game during Alpha, Beta and the main release. We'll have a default branch on Steam where we release major and tested updates. Interesting for rapid iterations is the Development branch, where we'll let any of our developers update data much more frequently. Sometimes this will break that branch, but a key differentiation to OA's beta patches: data updates are used more. Fixes are not primarily focused on the programmers. Also let me introduce you to our Senior Quality Assurance team member: Astaroth. He will be your Community QA Liaison - which means he'll help the team stay aware of issues being reported and voted on. That's not to say the rest of the team will not also be using FT: we are encouraging as many of our developers as possible to keep an eye on it. We hope CIT can continue to provide its excellent services to many other projects such as the community's. Please join us in creating a stable and optimized Arma 3 game
  20. Hello! Today we deployed our advanced helicopter flight dynamics model to the development branch. You can find more information in the recently released OPREP, but, in short: The advanced flight model is an optional feature, which we hope will make helicopter gameplay more authentic, challenging and enjoyable to master. You can switch to the advanced flight dynamics model in Game Options (section General) and try it with each helicopter we have currently in game. Please be so kind and share with us your experience! We're specifically looking for feedback on these these topics: Flight Experience - behavior and handling of helicopters GUI- layout customization, lucidity, informativeness etc. Controls - schemes usability, customization, controllers issues and related But we are grateful for all for your valuable, constructive and civil feedback. Oh, and don't forget, this is just a first step and we are still working on the RotorLib functionality, alongside the other key features of the Helicopters DLC. Happy flying!
  21. Hello! We finally deployed sling loading to the development branch and as usual we'd love to hear your feedback. But first some overview. Sling loading is by default available to all current helicopters except of AH-99 Blackfoot and Mi-48 Kajman. In Helicopter Movement section of Controls you can find two new actions related to sling loading: Rope Interaction (default keybind is B) and Sling Load Assistant (default keybind is Right Ctrl+B). Multiple objects (for example Supply Boxes, Quadbike, Rubber boats etc.) are configured for sling loading so you can just place them in editor and you are good to go. In future we will add comprehensive learning missions, at this moment you can just discover secrets of this new functionailty by yourself. Also as was mentioned in changelog, we added new scripting commands for sling loading so you can have fun with them too. Please be so kind and share with us your experience! We're specifically looking for feedback on these these topics: Usability - is sling loading understandable enough? Difficulty - is lifting cargo too hard or easy? Multiplayer - do you have any issues with sling loading in multiplayer? But we are grateful for all for your valuable, constructive and civil feedback.
  22. In this topic i want to point out, what i think is well made and what is not in the mobile game. I only list them, but i can specify them, if something isn't completely understandable. Pros: Procedural generated islands (so there is always a bit of variety) The possibility to carry a second gun The possibility to stack items (like bananas, bandages etc.) The aiming help (the red/orange/yellow/green circle above eventual hostiles) The possibility to hold flares to carry the light with you Cons: Automatic melee attacks (It would be better with those shock waves) The lack of multiplayer mode The durability of clothing is very low, making it necessary to use guns or avoid fighting I know that there are going to be some updates to improve the gameplay on both browser and mobile version, so i am sure the cons will be nonexistent or less in the future. Also, i have some ideas for MINIDAYZ in general: Releasing the game on Steam to make it accessible for more players. You could use Steam to create servers more easily, too. Improving the space system to make it a bit more logical. For example i can only carry 3 cans of kvas but at the same time i could carry 3 cans of fuel in a Taloon backpack. Just an idea. And last but not least, keep the good work up.
  23. Hello everyone. The new feedback tracker is a little bit complex to use. The new website is far from being intuitive. So I have decided to do a thread about this matter. Is possible that someone explains a little bit here how to use it correctly? I suppose that learning to use the feedback tracker could help to reduce the doble posting of the same game problems and to keep the information of the game issues up to date.
  24. I noticed this issue started after update 1.64, so I think that is when the bug got added when the search function also got added to Zeus. A lot of the objects that were able to be placed are not showing up for Zeus to place anymore. It looks liek they aren't missing entirely, they are just missing from the Zeus list. Most notably, off the top of my head: Objects like sandbags and hbarriers. There is also others that I can't remember, and who knows how many other missing items that I haven't come across yet. I didn't find any forum post on it yet, but I found these in the feedback tracker: https://feedback.bistudio.com/T120337 https://feedback.bistudio.com/T120735 https://feedback.bistudio.com/T120423 More here: https://feedback.bistudio.com/maniphest/query/9w_nsMfxZ7Ku/#R Any news on this getting resolved or if it is even being worked on?
  25. Forgive me if anyone else has suggested it, i didn't see anything in the forums about it, and my error messages aren't easily sent. I too have been suffering from the 3fps 'bug', and i'd like to make the following suggestion regarding submitting feedback. Is it possible to add 'send' buttons on the error messages so those could be sent directly to BIS? (I guess you'd need a dedicated SMTP mail server like JangoMail or similar to handle the log traffic, but this would likely generate more feedback for you guys.) I have no idea if this would help the DEVS to examine logs to see if any of the crashes share a common trigger, or if even the logs reveal such things. What i do know is that many users have short attention spans and probably won't take the time to share their crash data in the forums or feedback tracker, especially if they aren't yet Arma addicts. Here's my suggestion for sending error logs directly to you guys (in green) : Cheers and keep up the good work friends!
×