Ghoullees

I can tell you that spotting aircraft in real life is easier than what you are seeing on your screeen, so don't feel completely disheartened. The effects of shine, shadow, sun glint and other effects just cannot be translated onto a few tiny pixels 'miles' away. The 'Team Fusion' build of Cliffs of Dover' did a good 'glass glint' effect which made you at least aware that there was enemy in that direction, which inturn, allowed you to start scanning a specific piece of sky. However these are knife fight ranges already. Jet fighting, always going to be difficult. The advise of 'dont look directly' at a spot when scanning is good advice also. This is particularly true of nightvision. You see more 'shapes and obstacles' by looking to the side and up or down slightly. Practice, practice, and don't feel like you are alone!

As of 6 May this crash is still occurring. I have just loaded the Hawk, batteries on, tune radio, contact ATC to request Startup and crash. Have reproduced this 3 times. Other aircraft working on the map without issue. Ghoull, out.

RESOLVED: 1.5.2 installation error resolved with 1.5.3 Seems that 1.5.3 has resolved the previous version installation errors I was having. Don't know what changed, but kudos on bug fixing. Cheers.

No, my initial isssues were with 1.5.2. However, after trying to get the updater to function today, I simply get the DCS Title Screen and instantly it shows (Not Responding) on the window frame which is new. May try a reinstall with 1.5.3 and see if I have any better luck then.

Bump. Any suggestions or possible solutions gang? Still not working for me, though World 2.0 does. Very weird and very frustrating. Running Windows 10 just incase this is throwing in a version curve ball.

Hi all, I complete the installation, the DCS Logo and intro screen shows and then..... nothing. The Game window goes blank though the PC is still working. DCS Open Beta 2.0 works fine straight out of the box but I cannot, for the life of me, get 1.5.2 working. I have a machine above spec (Dxdiag attached). I've tried reinstalling X64 redist to solve .dll issues, and tried a full reinstall 3 times ( deleting Config files each time ) and completely deleting all previous folders for a complete clean install. Anti Virus is off and firewall off. No effect on getting 1.5.2 to load. Install Log file also attached. Install Version: 1.5.2.49392.141 Can anyone help? Cheers. DxDiag.zip autoupdate_log.zip

IKR! Flight Sim Basics 101. Logbook is your bragging rights. Log book is where you should be able to go to see, "Oh god, I haven't flown the P51D in 6 months" better do a refresher. So basic. So poor.

Log Book Errors [Fixed for DCS World 2] Logbooks seem to have been broken for sometime now, and I've basically pulled back on my flying as a result, not wanting to take on long compaigns and such until addressed. A robust multiplayer Logbook would be ideal as well, but perhaps only relevant on 'ranked;' maps or some such thing. If there is already a fix, I'd love to know what it is ( other than manually fooling around with .lua files - 'I aint got time for that crap!'. ) Time is money. Time is important. The Logbook helps keep track and a semi permanent record of those valuable hours.

This is a pretty poor bug. The Logbook is the ONLY place to keep track of what you do in DCS. Given the time and effort it takes to learn a new aircraft and get it off the ground, let alone fly sorties and blow stuff up, it speaks volumes of what ED thinks of 'player progression' and 'simple reward tracking'. Nice one ED. Way to go. 6 months this has been going on. I've decided to stop buying modules until the very basics are fixed.

Whew. Glad this is not just me, I was starting to go insane. Tried to add some Mi-8's to an existing map, and couldn't get ground units to activate so they had something to shoot at. Wasted an entire day trying to find a work around.

Moved USB ports and relogged into the game. The Axis Commands now show for some strange reason, and I have been able to map throttle and joystick subsequently. Strange. Not experienced that before, and all other games worked fine. Issue sorted for the meantime.

Unlike all other modules of DCS ( including the Huey ), I am unable to map my Throttle Axis to collective controls, nor am I able to map my joystick to Cyclic controls. The Key mapping in options registers all buttons, but apparently none of the axis. The one exception to this was the zoom feature under 'axis commands'. Me thinks a patch is required to match axis mapping as per the Huey.

Unlike all other modules of DCS ( including the Huey ), I am unable to map my Throttle Axis to collective controls, nor am I able to map my joystick to Cyclic controls. The Key mapping in options registers all buttons, but apparently not the axis. A patch is required. *** Apologies, just found the bugs thread, reposting this there.

Hi Gang, I'm a total noob and trying to create my first Mission in DCS. I'm trying to create a switched condition which will pop a smoke marker at various locations once every 260 secs ( trying to minimise frame rate loss ). I'm still a little confused on Flags and Values. I need to pop three different smoke colours, and they all need a switch on and then a repop condition. Does this mean I need a Flag 1 and 2 say for Blue smoke.... A flag 3 and 4 for Green and so on. OR Is it simply a flag 1 and 2 for the pop, and repop function, and the value simply is a random number unique to each smoke location? If anyone could give an example of the exact entry into the mission editor would be appreciated, as I have been looking at this far to long, and starting to loose my marbles. For clarity, something in the format below would be a big help. Switch Condition / / Conditions = 1. 2. // Actions = e.g 1. Smoke Marker Blue - 2. Set Flag # & Value Cheers guys, and happy flying.

Has there been any movement on displaying custom skins in DCS World Multiplayer yet?