resolved Freeze-crash when loading Supercarrier module, hangs on "sim post start"

[Jayhawk1971]

Hi,

I have this problem trying to load missions with the SC....and it is my fault! 

I messed with the GroundCrew.lua, because I wanted to "fix" the F-14A animation (raise launch bar). Unfortunately, this seems to have caused an error (according to the crash log) that freezes DCS at the mission loading screen.

To add insult to injury, I've also accidentally deleted the saved original .lua. 

Could anyone post the correct original aircraft data values, or the original lua, or would reinstalling the Supercarrier module fix this?

I'm referring to CoreMods/tech/USS_Nimitz/scripts/crew.lua

Thanks.

Edited February 13, 2022 by Jayhawk1971

[PLUTON]

équipage.lua

slt here is the crew.lua you are asking for
hope it will go

Dcs Open Beta/ CoreMods/tech/USS_Nimitz/scripts/crew.lua

équipage.lua

bon vol Pilote

[Jayhawk1971]

Thanks Pluton, much appreciated!  

Edit:

Oh, @PLUTON I just checked. I need the GroundCrew.lua, not the crew.lua.

If you could post the groundcrew.lua I would be a very happy camper.  

Thanks

Edited February 13, 2022 by Jayhawk1971

[Flappie]

Another solution if to run a DCS repair.

[Jayhawk1971]

vor 5 Minuten schrieb Flappie:

Another solution if to run a DCS repair.

I was kinda trying to avoid the hassle of that. I just got DCS where I needed it to be performance wise (VR). If it's only a simple value in some line of code a full repair seems kinda overkill.

I'll probably try to deinstall and reinstall the Supercarrier module. That should "reset" the .lua, right?

[Flappie]

I don't think so. I'm afraid it's part of the core files.

[Jayhawk1971]

Oh crap! Oh well, guess I'll have to bite that bullet. 

Thanks, though.

Goes to show: don't mess with lua's.

 

[Flappie]

Here you go.

GroundCrew.lua

[PLUTON]

GroundCrew.lua

here it is test if it works good if not make com flappie it is very good advice

[Jayhawk1971]

Thanks guys! I hope it works.  

[Jayhawk1971]

Thanks again, @Flappie and @PLUTON

I successfully got it to work again. For posterity: it was the value "7," and I suppose I was merely missing the comma (it's usually such a small detail) after the previous "404" value. 

Thanks

 

[PLUTON]

Yippee always happy to see a dcs driver that
was able to fix a problem.
good flight to you