Single player missions always paused? (2.5.5.32533)

[Wikkus]

Greetings, folks.

 

 

Apologies if this is answered elsewhere -- if so, my search/GoogleFu is weak :doh:

 

 

 

I've been away for a little while and came back very recently because of the Fw-190-A8.

 

 

I had an issue following the update to OB 32533 and had to perform a repair of my installation.

 

 

 

Everything is back to normal *except* I now find every mission I start, whether it's an Instant Action, part of a Campaign, or even a self-created one, starts in a paused state.

 

 

Is this a new feature? Can it be turned off (and how)?

 

 

Sorry again if I'm missing something obvious.

 

 

Cheers,

Rik

[Wikkus]

{bump}

Nobody? Just me? :(

 

Rik.

[BIGNEWY]

Hi

 

have you tried the pause break key on the keyboard?

[Wikkus]

Hi

 

have you tried the pause break key on the keyboard?

 

 

Hi Bignewy,

 

 

Yes, that unpauses the mission for me, but what I'm after is it *not* being paused in the first place, iyswim?

 

 

I don't recall missions starting in a paused state before; as I remember, one chooses the mission, hit "start" on the briefing screen, wait for the loading, then straight into mission. Except I'm going straight into a paused mission :huh:

 

 

Cheers,

Rik.

[BIGNEWY]

Sounds unusual for sure,

 

can you repeat the problem, then attach your dcs.log we may see something in them

[Wikkus]

dcs.log attached

 

Here's my log file, fresh off the, er, press :)

 

 

Load DCS; select pre-built mission (in this case, the F/A-18 "Valley Run"); hit "start"; game loads; mission presented in paused state (at which point I quit out to desktop to keep file size to bare minimum).

 

 

Cheers,

Rik.

dcs-log.zip

[BIGNEWY]

I am seeing some errors in your logs.

 

Try a cleanup and repair to remove any modifications of the core game.

[Wikkus]

Second try...

 

I am seeing some errors in your logs.

 

 

Noted, thanks.

 

 

Try a cleanup and repair to remove any modifications of the core game.

Done and done.

 

 

Re-ran exactly as before and noticed some of the aforementioned errors still there and these were pointing to independent/third party add-ons installed in the preferred "%USERPROFILE%\Saved Games\DCS\Mods" location, e.g. VPC ground objects, 476th Range Targets, Civil Objects, etc., so these were culled leaving only Tacview, the community A-4 and the Civ Aircraft mods.

 

 

Same result.

 

 

So, culled Tacview and the two aircraft mods so there are *no* non-core mods at all (/cry) and yep, it's still starting in a paused state.

 

 

I hasten to add that despite this annoyance, everything else in game works absolutely fine and dandy.

 

 

Cheers,

Rik.

dcs-log-2.zip

[BIGNEWY]

I would suggest renaming your dcs folder in saved games.

 

Keep it as a backup for now and then restart dcs, login and redo your settings and test.

 

you can move inputs and so on after the test to the new folder.

 

this will rule our settings issues as I am seeing errors in config files.

[Wikkus]

I would suggest renaming your dcs folder in saved games.

 

Keep it as a backup for now and then restart dcs, login and redo your settings and test.

 

you can move inputs and so on after the test to the new folder.

 

this will rule our settings issues as I am seeing errors in config files.

 

 

Done, and that's fixed the problem :thumbup:

 

 

New logfile attached as I'm still seeing a few warnings/errors, although at least one of those -- CE2-related -- I don't have the module for anyway.

 

 

 

Incidentally, there's now the familar briefing reminder/splash screen with the "Fly"/unpause/begin mission button on it, something I'd overlooked was actually missing.

 

 

Now just to figure out what I can move across from my backup -- the bindings LUA files are quite obvious, but is there anything else that needs to come across?

 

 

Cheers,

Rik

dcs-log-3.zip

[feefifofum]

Your control bindings should be the only critical item; if you have any custom missions moving them back as well shouldn't cause any issues.

 

If I had to hazard a guess, something in your video settings was causing the UI to appear somewhere other than where it should have been, and the issue is likely in options.lua which you can safely leave behind; you'll just need to reset preferences (sounds like you'll want to make sure easy rudder and takeoff assist is turned off for the Anton, for example)