tomudesu

Thank you for your continued support of the Gazelle. I really appreciate the meaningful and thoughtful effort you and your team have put into your work.

I know I am bringing life to a dead thread, but after finding this thread, I found another good source for the 2003 operation

Tried Instant Action, Cold Start Caucasus. Started up, tuned radio, released parking brake...couldn't move. Realized there might be wheel chocks, but can't open a comm menu in either standard or easy comms. Using Vaicom.

Red defeats Blue soundly in many Red Flag exercises. But I do feel your assessment is correct, as the AI is simply not doing things the way they should be doing things in SEAD and whatnot.

Thanks to MAXsenna, I got it sorted out; it was the UH-60L mod in the saved games folder that was somehow conflicting. I hope that helps other in the same boat!

Thanks so much for getting me pointed in the right direction! I got it sorted out. You clued me in to check my mods, so I renamed all of the mod folders in saved games to -old. Vaicom added the tech back first start, so I knew it was looking in the right places. I used good old Navy Nuclear Power School half-splitting after that to reintroduce the folder and narrowed down the repeatable error to the community UH-60 mod. Kept that in the -old folder and now everything works. Thanks again!

I think is may be related to the listening suspended problem, but within a mission, the unit keeps resetting, and with it the comms panel opens. I have tried resetting VAICOM, ensuring the locations are correct, and even tried going back to the .24 version, but still having the problem. Thanks for any advice in advance! VAICOMPRO.log Export.lua

Did anybody ever get this sorted? I have spent the last couple hours trying to figure it out to no avail...tried all the advice here :( VAICOMPRO.log

Same for me on a 4K monitor.

Same issue here. Press trimmer, controls lock. Have to reset trimmer to gain purchase over controls again.

Thank you! Works perfectly now.

I get several Mission Script Error popup on loading any mission. Weapon fire and weapon impact also cause Mission Script Error popup. I had an SSD that lost connection during the latest (2.5.6.59625.1) Open Beta update. Tried a repair, but it didn't fix the problem. Sorry for my ignorance with these matters! Attached is my DCS.Log Thank you for your help! dcs.log

Thanks for your help in advance. I am sure I am missing something simple, but after the DCS 2.5.6.49314 Open Beta update, the TGP will revert to a stowed 180 position when Cage/Uncage is pressed. Is that proper behavior? If so, what is the best/fastest way to get the TGP slewed to a point in front of the aircraft? Thanks again for your help!

I noticed this "feature" as well. I noticed and then tested the cable cutter on the UH-1. I think the cable cutter is bugged as it didn't protect me from the invisible wires ;)

Just wanted to second the kudos! Great job!

Greetings and thanks in advance for any help! I updated to 1.5.3.53279 today, and the game loads to the Main Menu that is tiny. I have tried editing the options.lua, missioneditor.lua, repairing, turning off Occulus Rift, but it still starts with a basically unusable menu. The game will run in the tiny resolution as well. The 2.0 Alpha, and Open Beta work just fine. Thank you for any help!

Yes!

I will second that emotion. Well done. The level of systems detail is amazing. I have never flown an Mig or an F-86, obviously, but the difference in the feel between the two models is unlike anything I have ever felt in a flight simulator before. Inspiring work you have accomplished.

The best part of life is having a plane worth waiting for. I am simply thankful that this incredible simulation exists at all. It is the simulation of my dreams.

I want the Mig.

If there is demand, it will be made. Somebody is going to have to test the waters first though. I would love civilian aviation options. Some many planes, so little time.

My Great Uncle flew P-51s, and he specifically talked about how a senior airman in his wing told the new guys when they couldn't shake a bad guy that they call it over the radio and then they should pull the stick until they begin to lose vision, and then count to 3 or 5 or something like that and release. He said they would always be in the clear after that and if the bad guy tried to follow, a friendly would be on him. Now of course, they weren't pulling 8g most likely, but they were being told to pull hard.

Awesome. I am in. Will attach my pathetic attempt at artwork as soon as I find my crayons!

I have the same issue. Thankfully for me, a computer restart always solves the problem. I think your idea about the activation is valid, but only if the activation check occurs only once every 24 hours, because for me, a restart always allows me to run the program. But the next time I try to run the program after more than 24 hours, I get the same problem.

I already had the latest versions of C+ and DirectX. Well...I wanted to see if it was hardware or software, so I reinstalled Windows, which is something I have been meaning to do for a while. I upgraded from Win' to 8.1, and DCS World runs flawlessly. Sometimes starting over is just the ticket. Thank you for your help!