rayrayblues

On the ground or carrier deck, I call for start up, no response. When in the air, comms menu doesn't appear. :doh: can't call for inbound etc. This just started happening today. It was fine yesterday. :( Cleanup and repair does not help. dcs.log

DUH...I have never had to use that button before in 18 months of playing DCS. I'm seeing a lot of bugs lately. I hope they have an update soon to fix some of this. OB is almost unplayable. I could always use stable, but then I wouldn't be able to use any of my newer modules. SC, FA-18, P-47, etc. I figure that since I paid my $$$ for these, I should be able to use them. Thanx Buddy

These units were attached to the SC. As I zoom in and out it gets more weird. I cannot zoom in close and place units on the carrier or anywhere on the map. I closed DCS and rebooted the computer, then ran cleanup and repair, no change. It was working fine just a few minutes ago. Anybody else see this??

Try as I may, I cannot get the rescue helo to stay with the carrier. According to Wags, set helo altitude to 100 feet and speed the same as the ship. Every time, the helo flies faster than the ship. Same with Kuz and Ka-27. Am I missing something?? I just noticed. It's not the helo speeding up, it's the ship slowing down. It starts at 25 knots, then in a few seconds it slows to 11. OK NVM. I think I got it. I added more waypoints for the carrier and now it doesn't slow down.

I got it working. Looks like I haven't updated my graphics card driver in a while. I ran the update and the game loaded just fine. Thanks for being there for me.

You need to set other units as client in order to have them available to fly. The selection window should open. Double check to see if they are still set to client.

Dude, read what Ironman said.

Hi BN, Thanks for getting back to me so soon. Win 10/64 Ver 2004 Last update yesterday July 1st. Samsung 860 EVO SSD CPU - AMD FX9590 4.7Gb MoBo - Asus 990 FX Sabertooth RAM - G Skill RipJaws 32Gb DDR3 GPU - EVGA GeForce GTX 1660 Ti 6Gb DDR 5 PSU - Prestige ATX-PR 800W Cooling - Corsair H80i v2 all in one. Pretty beefy for an older machine. Hope this helps.

When I try to open the game, all I get is this error message. Tried a reinstall and get the same thing. There are no log files as I haven't done anything yet. :helpsmilie:

Or....my plane or helo just decides to commit suicide a few minutes into the replay diving into the ground or ocean. A good example: I took some AAA damage in my P-47 and decided it was best to fly back to base and repair. On the way back, my cowling and propeller came off, but I still made it back to the AF and landed. I thought that this would make a really cool video, so I fired up Bandicam and was ready to record. Needless to say, my plane decided to do a swan dive straight into the ocean about 5 minutes into the replay. :doh: I never even made it to the battle area where I received the damage let alone to the cool part when my prop came off and I was still flying. :cry: Perhaps it's time for a new replay system, or just try to fix the one we have. :thumbup:

Not to mention the new haze effect. RCtrl + O may make it brighter. or not. :D

Rather than rollback, have you tried un-installing the module and then restarting the game? It will prompt you to install it again. It worked for me a couple of patches ago.

The devs can't do it all, otherwise like "wholehawg" said, we would have to wait for years. Beta testing is standard procedure with these types of games. (War Thunder, WOW, WOT, etc. The devs get it working as well as they can and then let the players find the rest of the bugs. It's annoying for sure, but this way we have thousands of people refining the game and it goes much quicker. All new modules are open beta first. If you want to play P-47 or SC you have to have OB. Sorry dude. that's just the way it is.

Okay, I agree that it's over done. You're right about the humidity. They could back off on it a bit. The Persian Gulf is not dry as F***. The average humidity in Dubai is 80 to 90% with temps as high as 120F. Nevada is much like Phoenix Arizona where I live; 8 to 10% humidity from April through June with temps avg. 105 to 115F. In July and August, the northerly flow of moist air from tropical Mexico meets the hot dry air and creates massive monsoon storms; raising the humidity. In contrast, NTTR is a sauna and PG is a steam room. The haze would be more likely in PG.

Looks real to me too. I see it every time I take an airliner. Actually, it should increase with distance and virtually disappear close up. It's the thickness of the atmosphere. More distance, more atmosphere.

When placing vehicles on a FARP, whether static or active, they sink in. The only way to get around this is to place the vehicles off to the side and have them drive up to their locations. It happens on Normandy and Persian Gulf so far. I haven't tried Caucuses yet.

Me too! I was flying my P-47 and took some damage from AAA. I made it back to the AF and landed. Along the way back, my cowling came off and also the propeller, but continued on to make a perfect landing at Khasab. I thought this would make for a very interesting video, but the replay showed me crashing into the gulf before I took the damage. Go figure....

No, Mbps

Thanks DFA, I did and now it's working; somewhat. (see above) :cry:

Thanks. This is true, but I found that even though you can't call "inbound," if you land and shut down your engines, it will reset to "request start up" and so on until you want to request "inbound" and you're back where you started.

I'm doing 4.6 :smilewink:

DUH :poster_oops: I knew that. Thanks. It sure does help being in the right folder.

What am I doing wrong? For the life of me, I can't seem to be able to access ATC at FARPS. Ground crew comms work just fine, but whatever I do I get no response from ATC. I am flying the UH-1-H. :helpsmilie:

There are numerous threads about this issue including one from myself. This is the answer that I got from BigNewy. https://forums.eagle.ru/showpost.php?p=4296847&postcount=2

I don't know. It doesn't work in cmd either.