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?

Hi Runibl, Yes it is. I've tried every combination of setting Intercom and VHF that there is and nothing will make the radios work. My last port of call is to make sure frequency changes are done slowly, and perhaps map some Mic switches ( as I don't have a Warthog stick, I've never bothered to map these ). Cheers for the attempted assist.

Thankyou all for your input and offers. I have to say that I am aware of everything that has been suggested, with the exception of the radio assist button ( pretty sure that is on but will check ), and also I may need to map some radion transmit buttons to keys. Until now, I have been using function keys only. At present, still not luck, and no consistency with radios. Have to say this has been an issue since early versions of DCS-Anything. Radio programing (ATC or JTAC) is pretty poor, and a known and accepted BANE for map makers too.

Found this at least, but still so much to wade through.

I've expreienced this incessant rolling let and right, with a balanced loadout a couple of times. The first time was due to Autopilot throwing off the trim, which could be corrected. However severl times since, I have taken of, done a few maneuvres and then CANNOT trim out the roll left or right. It happens maybe once in 5 missions, quite irritating. Has there been any closure on this? Cheers.

Hi All. Been playing DCS since Blackshark, and I have ALWAYS found radios ( even on easy comunication ) REALLY, REALLY flakey. At the moment, in A10C I'm not having luck with contacting ATC, or Ground Crew reliably. At the moment: 1) Setup radios to correct frequencies 2) hit / for the comms menu 3) Up on screen comes 'Interphone' followed my 'MAIN', then all the comms options. 4) Select ATC for the correct airport 5) request.... anything .... nothing. In single player campaign I cannot talk to my wingman or anyone else, ever since 1.2.. . . . with easy comms selected. Tried in sim mode by changing the selector dial on the Interphone and still not joy. I know very few new players that can use the radios reliably. Can anyone advise: 1) If this is glitched since 1.2? 2) Have hidden 'steps' been introduced I dont know about? 3) Is there a post on this very topic I've missed; and 4) is there a 'Search' function in these forums? Regardless, whatever I try, doesn't work reliably. And this has been the way of it since the original Blackshark. Is there really no way to simplify and make in-game comms more reliable. Any and all help appreciated. Cheers, Ghoull

OK, this may explain why I am having trouble in both A10C and Ka50. My comms menu wont appear, or if it does, ATC, JTAC and Wingmen do not respond as the radio is stuck on Interphone. I am aware of the dial that should be pressed/turned to get OFF Interphone, but the radio seems stuck there on A10C no matter what I click, and Blackshark just doesnt GIVE a comms menu. Now you say we need to fool around with .lua files? What? Not acceptable. This is a bug that needs to be addressed and fixed. I, the paying customer, am not the one that should be having to delve into files to makes corrections to your product. When a patch arrives, it should UPDATE and fix issues. Previous files should not overide the new version. Craziness.

Yep, having the same problem here, but not just with JTAC, but ATC ( has that ever worked properly, consistently?). I am checking frequencies, recalling, and recalling, and nothing. For a couple of campaigns I was unable to speak with my wingman as the radio was permanently stuck on intercom. No matter how and what I tried, I couldnt speak with anyone. Radios have always been pedantic. Amazed this hasn't been simplified and cleaned up. Is it still necessary to wait one second between frequency change mouse clicks, like it was back in Beta?

:thumbup: Dragon, you're a legend. Keep up the great work mate. Note sure where the DCS community would be without your enthusiasm. Your maps are top notch, and greatly appreciated in Australia. Looking forward to the weekend update, but also more than happy for you to test 'till it's done'. We're kind of mystified why ED doesn't have some professionally produced missions to come 'stock standard' with DCS World, for ALL modules, to at least get people started and inspired. :huh: This is even more relevant now, as more and more people seem to be 'stopping by' the game to 'check it out for the first time'. Not having anything to play with out of the box seems like a really poor Dev, Business, Creative decision....that is to say.... bad decision all around for all parties. In God We Trust, God Save the Queen, God Bless America, BUT THANK GOD for Dragon. :)

Well, no you cant just play them with 'any third party player'. Tried, Quicktime, Microsoft Player, Nero and DivX, none of which will play them. VLC is made by which garage company?

Ok, so I think I have a bit more of an idea on this one after playing accross multiple server types, in multiple aircraft. FIRST: When the A10C aircraft is played in multiplayer, on a Blackshark based server, the A10C HUD displays a much larger font and display than normal, thereby only allowing less than half the HUD data to be viewable. The rest appears off screen. And NO! This is not HUD drift data from wind, etc, etc which everyone throws about as their throw away response. The HUD data is clearly set at a different, and incorrect point of view, or .lua value in the Blackshark files. This seems to only occur for A10C cockpits being played on Blackshark Multiplayer servers. It seems the Blackshark server view settings for the A10C are different from A10C Server cockpit view settings. Devs: Is it possible to syncronize these settings so both cockpits view correctly, regardless whether multiplayer is run as an A10C server, or a Blackshark server? Some continuity in play accross both platforms would be brilliant. Should be easy to tweak and patch. SECOND: In addition, the TGP in the A10C is VERY inaccurate on a Blackshark server. On my run tonight, the TGP would not slew smoothly or accurately, and then stay on a target. It would jump all about everywhere except the target ( almost like the old A10A problem in Flaming Cliffs! Actually, exactly like the A10A in flaming cliffs ). Mind you, the problem I was having was that the TGP was zoomed right in, with target direct ahead and in frame, and would still not allow centering to point track mode on the target. It seems that some of the multiplayer settings for A10C cockpit views need to be reviewed for continuity accross both server types. Strongly recommend this is given a going over as the lack of data on the A10C makes this almost unplayable with our Ka50 friends, without reverting our dedicated server over to a complete A10C server. Having fun otherwise! :pilotfly: Ghoull