[PROBABLY FIXED B933] "Object reference not set to an instance of an object"

[mavfin]

Is there someone already going through the community pack 35 and checking what's still good and what's not loading, or does the community need to look at it?

[Dimitris]

Yes it's being taken care of.

[Dimitris]

Fixed with release of updated community scenario pack.

[Fer_Cabo]

Hi folks,

I strated getting this same Error-Message a few days ago when trying to load a saved-edited scenario i've been building for weeks "on top" and enhancing the Steam Workshop "Korean Campaign, 2018".

I had had no problem at all whatsoever thus far with previous savings as i progressed with work adding bases, units, satellites, attachments, etc.

I fear i might have lost all work put into it. Is the solution going to come for this one with the updated community scenario pack when that update is released?

[Dimitris]

Hi Fernando,

The problem was in the part of the scen-rebuilding code that deals with removing magazines from a platform, based on instructions from the .ini file. The code-side fix is already in the v1.12 RC and now the community scens have been properly rebuilt as well.

If you don't have any healthy past copies of your scenario, please send it over and we'll try to restore as much of it as possible (no promises).

Thanks.

[Fer_Cabo]

Thanks a lot Sunburn... Here it goes! Fingers-Crossed [&o]

[User1984]

The Scenario - Facing the Dragon, 2014 is still showing a database error.

Please see my post in the Tech Support Forum today.

[mavfin]

Yeah, I'm looking at this. If you have Steam, try the single version of Facing the Dragon from the Workshop. None of the Community Scenario Packs' version of this scenario are any good. The item number changed somewhere between DB3000 429 and the Community Scenario Pack 32 and above.

Anyway, check the tech support thread.

[Dimitris]

ORIGINAL: chops
The Scenario - Facing the Dragon, 2014 is still showing a database error.

Please see my post in the Tech Support Forum today.

Different issue.

[Fer_Cabo]

Still no progress on this?

[Dimitris]

That one is completely un-salvageable. Sorry!

[Fer_Cabo]

Thanks anyway! However, is there a way to prevent this to happen in future saved-editor-scenarios?

[Dimitris]

Well, from our side we're fairly certain this issue has been eradicated in code. On the scen creator side, it's never a bad idea to keep recent copies of a WIP scenario as fallbacks. A source-control system can make this an ever smoother workflow.

[Fer_Cabo]

Thanks! But... never heard of a "Source-Control system". What is it about?

[mikmykWS]

Git or something like that. He's suggesting you try using a backup system with versioning etc.

[michaelm75au]

For Steam, each pack is being uploaded as a pack (#24, #25, etc), and as a separate pack with the most recent changes. So subscribing to the separate pack give you the most current versions of the scenarios, but you have a fallback of getting the old packs also.

[sufa101loofa]

I am playing the Korean Missile Crisis scenario. I have launched my Tomahawks when I started get the following exception message windows:
1) OnThreadException - once I click Ok the next message comes up ( all the while the game continues to run )
2) The Ex != null
3) e.Exception GetType()Name.ArgumentOutOfRangeException
4) The message index was out of range....
5) the exstack trace at.....
6) and then it loops back to the first message.

I can not exit the game nor make changes while the message boxes appear.

Frustrating...

[Dimitris]

Hi,

Can you show us a screenshot with the error message with the stack trace, and also post the autosave file?

Thanks.

[sufa101loofa]

Screenshot - save file to follow

[sufa101loofa]

Saved file