Acedy

Well there is more truth in the first part of your statement than you might think. I completely agree that collidable trees that block the AI's view are needed for a helicopter sim, however 100% collidable trees aren't realistic either. If your read "Chickenhawk" for example you will be surprised about the stunts Huey pilots in Vietnam pulled off to get out of a small clearing when they couldn't hover and climb vertically. They flew right through the treetops, cutting off branches with no or little damage to the rotors. That's why I would like to see a more sophisticated tree collision model that does not just distinguish between no collision at all or 100% collision = crash.

Just out of curiosity, did you enable or disable it?

As you can see, the English forum has been restructured so that it now fully supports the new DCS series. Here is a quick overview: The forum now contains five main subforums: "DCS", "Lock On", "Simulation", "Reality" and "Customer Support". In order to avoid a too large main forum page, we have decided to create several sub-sections for the "DCS + Lock On General Discussion" sections as well as the new "Multiplayer" section, which can be accessed from the top of the respective section. From now on please start threads in the section that your topic fits in best. Additionally, the new "Announcements and Updates" part will be used to release important official news regarding DCS. The section itself will be closed, this way new people can quickly get an overview about what is going on, but of course we will start discussion threads for important announcements and link them in the announcement. Finally there is a new section for "Multiplayer" with sub-sections for Lockon and DCS, where you can announce servers and squads, and a new "Cockpits and HOTAS" section for discussing your cockpit setups, sharing joystick profiles, asking questions about LUA exporting features and the upcoming "Physical Cockpit Interface Package (PCIP)" etc. So, what do you think about the new structure?

One thing to remember is not to quote a spam message. The reason is that while spam usually is usually reported and removed quickly, your post may not be noticed by the mods and it will actually serve the spammer's purpose, i.e. Spamdexing.

If you think that you have found a bug, please do the following before reporting it: 1. Make sure that it is actually a bug. DCS is a complex simulation, and what you might experience as an issue may in fact be a feature. Please refer to the manual and the User FAQ >here<. 2. Install the latest updates and patches. There is a chance that the bug has already been fixed. Please note that you can only get technical support for a fully patched and updated version of DCS that does not use any 3rd party modifications. Updates and patches can be downloaded for free from >here<. 3. One thread per bug only. Search this forum section if the bug has been reported before and if there is already a (temporary) fix available. If the bug has already been reported, use the respective thread to add a confirmation, alternative steps to reproduce it (if available) and your PC configuration. If you are sure that you have found a bug that has not been reported before, please open a new thread with a brief but meaningful title and use this form to report it: When using that form, please follow the guidelines below on how to report a bug properly. Bug description: The description of the problem should follow the 3C rule: it has to be complete, clear, and concise. This will ensure that the tester/developer can correctly understand your bug description in the first read-through, which will save a lot of time. Please do not only describe the bug itself, but also the correct situation that you would have expected. For easy reference it may also be helpful to add a quote from the manual (+ page) where the correct result is described. Do not forget to mention the DCS module/version that you are using. Steps to reproduce / Conditions of occurence: The testing team has to reproduce the bug before it can be fixed. If the bug is reproducable, decribe the steps to reproduce it (if they are not obvious). If the bug is not reproducable or only occurs intermittently, this should be stated. In that case provide a description of the conditions and circumstances under which the bug occured. If alternate steps or conditions are possible in confirming the bug, they should be listed as well. Also add any additional information that you think may be helpful in fixing the bug. PC Configuration Briefly describe your PC configuration. The following information should be included: 1. Processor 2. Motherboard 3. RAM 4. Video Card and Driver version 5. Type of CD/DVD drive 6. Internet connection type and performance 7. Control devices 8. Operating System and installed updates/service packs 9. DirectX version If you are using any special hard- or software while running DCS, please mention that as well. Attachments It is essential to add material for investigation, which demonstrates the bug in an obvious manner. This could be: Screenshots (with highlighting) Track Files Error Messages Temp folder including Logfiles Console reports Missions If you provide a track, it is very important to note the time at which the bug can be seen. Tracks are recorded by default for every flight, so if a bug occured simply save the track from the debriefing screen. Individual Logfiles can be found in the ".../Eagle Dynamics/Ka-50/Temp/" folder, however, it is a good idea to provide the whole "Temp" folder content. If the bug is reproducable, please delete the content of the folder first (but not the folder itself), then run the game until the bug occurs, and after that attach the Temp folder, which now includes only the newly created Logfiles. Just remember that multiplayer tracks are currently stored in this folder, so be sure to review the contents before deleting. Note that if you use Vista and installed BlackShark into the default Program Files directory, then the Temp folder might be empty even though a crashlog has been created. To access it press the "Compatibility Files" button in the Explorer's toolbar. The console can be viewed by deleting the "--console" parameter from the desktop shortcut properties. To do that, right click on the shortcut that you use to launch the game, select "Properties" and the "Shortcut" tab, then delete the "--console" command line parameter from the end of the "Target" field. Once you start the game the console will appear. You can add the parameter again after taking a screenshot of the console messages. If there is not enough space to store the attachement on this site, please upload it elsewhere and provide a link. Finally remember to check your bug thread frequently, as the testers/developers may ask you to provide additional information. And please be patient if you do not get instant replies, every report that fulfils the above guidelines will be investigated, however, this may take some time. Many thanks for your help and understanding.

Try to enable or disable the alternate pixel center in the Direct3D settings, I know that in other games this sometimes helps to cure the weird "fonts" you can see on picure 3, maybe it works here as well.

See manual p. 2-10 and 6-8:

Yes, you have to request them from ground crew before take-off and then activate them just like the HMS.

Interesting comparison, I didn't know that there is a Crysis: Pacifist ;)

http://forums.eagle.ru/showpost.php?p=568724&postcount=17 ;)

Maybe your download is corrupted or didn't finish properly? I would redownload the file(s) and try again.

I didn't try this but I guess you could also grant yourself writing permission for the Ka-50 or ScreenShots folder.

Shrubbo, I merged your thread with this one.

I think he wants to know if you are running XP or Vista.

Okay, as promised I have done a test, and for XP I cannot confirm this. PC specs below, used the following settings: WinXP SP3 1280x1024 Catalyst AI set to advanced 8AF, 4AA Highest settings in BS Recorded 5 minutes of a track using FRAPS. The result was that in both cases FRAPS showed exactly the same values for min., max. and average FPS (avg. rounded to one decimal). There was one difference though. I logged CPU load with task manager, and when the affinity was set to one core this core had a load of ~75% and the other of ~50%, whereas when I set the affinity to both cores each of them showed a load of ~60%. So if this tweak works, then it seems to be restricted to Vista.

That video can be found here: http://www.virtual-jabog32.de/index.php?section=downloads&subcat=30&file=807&lang=en

I gave this a quick try yesterday and I couldn't see any improvement at all, but I will do another more extensive test later.

Did you place both files in the same directory? Because apart from that you don't need to do anything with the data.cab archive. EDIT: hehe, too slow.

Try to install and run BS with administrator rights. And if that doesn't work, disable Vista's user account control (UAC) when starting BS for the first time. After that you should be able to activate again.

Fellas, we have gone through this many times before, if a decision is made the result will be announced, so it is useless to start a new thread every few weeks. And no, the release of BS has not been completed yet, only the Russian version is available so far. Closed.

Happy Birthday mate!

As this is the English section, could you please provide a translation or at least a short summary of the essentials when linking to pages that use other languages? Thanks!

Also check this post on how to use trim properly: http://forums.eagle.ru/showpost.php?p=571073&postcount=26

Hey Feuerfalke, thanks for the heads-up, however, this comes a bit too suddenly for me, I already have something else to do this evening, besides that preparing for a show like this would require a lot more time. And I'm not that photogenic anyway... :geek: ;)

Everybody who has registration problems please report them in this thread: http://forums.eagle.ru/showthread.php?p=570685#post570685