deamonesque

When you get an update it resets any custom .lua files. So you have to put them all back again. I have a .bat file to do it.

here: Except yours will probably be a different number than -0.95 as my monitors are different sizes and i wanted it in the middle of screen 1. But start with that then modify.

Very entertaining and engaging campaign. Kudos all round. Thank you for posting this. :pilotfly:

Ok. Thanks Creason. Yes the hardware has a small imballance but many probably do out there. As I say, this was never an issue before about a couple of weeks ago when it engaged everytime no probs even if I had a small amount of weight on the stick. So there is not a lua file to adjust I guess. Anyway thanks for the pointer on how to make it work now. I hope this post is usefull for anyone else with the same issue.

Ok. I think the behaviour has changed slightly. You now must have zero stick input when you click nose wheel steering for the autopilot to engage....

Hi F Creason, Ok. That appears to be it. Did that change or get tweaked in the last update? It did not seem to behave like that before? I did notice though that if my stick has a lot of jitter in the neutral position this was read as input and the autopilot would not engage. I added some big dead zones in it then it worked. Is there a .lua file that can be adjusted to set the tolerance of reading the zero stick input to the autopilot? Thanks.

In that mission you can go to the stern of the ship, line up on the landing strip, brakes on, full flaps, full afterburner, release and just get airborne. Then just complete the mission yourself. Subsequent missions ai has been ok so far.

Weirdly, I am no longer able to get the autopilot to engage with the AP Ref button In the F-14. The A/P Ref light comes on on the dash when I turn the autopilot on, but pushing the Nose wheel steering button no longer turns the light off off or engages the autopilot. Probably happening since the last update?? Update: I have just uninstalled the F-14 module, deleted all F14 folders in coremods and mods aircraft folders, also removed all my saved games folders, and had them rebuild by doing a repair, but the problem persists. Anyone else having this problem? Thanks.

Weirdly I now have the same issue as RSharpe had. I am no longer able to get the autopilot to engage with the AP Ref button. The A/P Ref light comes on on the dash, but pushing the Nose wheel steering button no longer turns it off or engages the autopilot. Probably happening since the last update? Anyone else having this problem? Thanks.

Yeah. First just rename the Saved Games/DCS folder and start DCS. Then if that works, replace back in all the old folders and files in the old DCS folder except the metashaders folder(s) the config folder and the fxo folder. Then if that all works, try also replacing the input folder inside the config folder. Good luck.

For me it was something in the Saved Games\DCS.openbeta\Config Folder that must have got corrupted. Replacing that folder fixed the problem.

For me it was something in the Saved Games\DCS.openbeta\Config Folder that must have got corrupted. Replacing that folder fixed the problem. :smilewink:

OK. hopefully good news. I found an older post here that renamed their Saved Games/DCS World folder. That regenerates the folder when you start DCS and that got mine going again. Now to copy back as much as I can to see what actually breaks it....

Hi Garry, OK. hopefully good news. I found an older post here that renamed their Saved Games/DCS World folder. That regenerates the folder when you start DCS and that got mine going again. Now to copy back across as much as I can until I put in something that breaks it to figure out the problem. Hope that works for you too.

AC5, What campaigns are there for the TF-51 that you deleted? Was it one you downloaded. There don't seem to be any loaded by default.... Thanks.

The lines in the log file around the error look the same as yours.

I have the same problem after my machine crashed. Ijust started a thread about that so will let you know if I find a solution. Going to try your replies fixes too.

Hi folks, I have the problem that my machine crashed while playing DCS and now it will not start. DCS comes up in windowed mode (which it is not supposed to) with the DCS Splash screen, then that goes away and a black screen is all that remains. Have left it for 30 mins but still remains the same. I have attached the log file here. The issue seems to be these lines: 2019-03-29 04:07:04.805 ERROR Lua::Config: Lua error [string "./MissionEditor/modules/TableUtils.lua"]:3: assertion failed! in "Scripts/autoexec.lua" 2019-03-29 04:07:05.054 ALERT Dispatcher: Error starting Game GUI: [string "./MissionEditor/modules/TableUtils.lua"]:3: assertion failed! I have deleted then repaired the autoexec.lua and the TableUtils.lua with the same problem still. I have also deleted and repaired several other .lua files mentioned in posts from other people with similar problems but the problem continues. Also deleted the metashader folders and the fxo folder. This problem is in my 'Open Beta' version of DCS. The 'Stable' version starts up as per normal. I have just uninstalled and reinstalled my beta version completely but the problem still happens when I try to start it. I am now wondering if it is a registry error problem???? Is there anyone clued up on the log files or DCS startup that can assist? Thanks in advance, :joystick: Dean dcs log.zip

And then again....

Firstly it has to be said: Rik, Nineline, and all the ED team I absolutely LOVE your work. Outstanding stuff. Secondly I was having similar CTD issues with the Caucasus map but strangely only with the "F-15: The Georgian War" campaign missions. Hotfix 3 seems to have fixed that too, so all good. Thanks a lot.

Fixed in open beta 2.5.1 Thanks again ED.

Hi ebabil As above, this problem is now fixed in the open beta version 2.5.1 I guess it will be updated in the release version in due course.

Outstanding ED. This game rocks again! Thanks heaps. 2.5 is fantastic. (Every landing you walk away from is a good one):joystick:

OK. Thanks for that info. Sooooo, which version should we be using? The open beta still, or the release? A) do they both still work on the multiplayer servers? B) will the updates be tested first on the open beta then ported incrementally to the release? It seems to me that there is already improvements in the release because the load times on the multiplayer is faster and it seems to consume less RAM..... Which is all good as far as I am concerned.

Looks like the release version of 2.5 also has this problem still. Can anyone else confirm? :music_whistling: