[PROBABLY FIXED B933] "Object reference not set to an instance of an object" (Full Version)

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Tech Support



Message

ZoroastroBR -> [PROBABLY FIXED B933] "Object reference not set to an instance of an object" (4/5/2017 2:03:13 AM)

Hey guys,

I tried to play a scenario from the community pack (latest one from WarfareSims website, running on Steam Build SR7 nine hundred and six point twenty six). The scenario was "Closing the Kurile Gap". I had the same error trying to play a few other community scenarios too.

Is there a fix?



michaelm75au -> RE: "Object reference not set to an instance of an object" (4/5/2017 10:37:03 AM)

Sounds like you are missing a database. Run the game Steam integrity check



ZoroastroBR -> RE: "Object reference not set to an instance of an object" (4/5/2017 12:56:49 PM)


quote:

ORIGINAL: michaelm

Sounds like you are missing a database. Run the game Steam integrity check


Didn't work!

Steam validated 37 files but I'm still getting the error



ZoroastroBR -> RE: "Object reference not set to an instance of an object" (4/5/2017 1:42:20 PM)

Did a fresh install, still not working.... same problem!



ZoroastroBR -> RE: "Object reference not set to an instance of an object" (4/5/2017 1:47:15 PM)

I downloaded the scenario pack 34 from Steam's Workshop and I got no errors. All scenarios are fine. I think pack 35 is broken.



mavfin -> RE: "Object reference not set to an instance of an object" (4/5/2017 9:22:21 PM)

The latest pack, which I believe is 35, is fine. I'm using it.



MorningDew -> RE: "Object reference not set to an instance of an object" (4/6/2017 1:43:40 AM)

I am getting the same error with 35

[image]local://upfiles/22361/90CF1D0A30C34C07B9D83C4994100E5A.jpg[/image]



Rain08 -> RE: "Object reference not set to an instance of an object" (4/6/2017 3:44:09 AM)

IIRC, it has something to do with the scenario's units. If there were any modifications done on a unit, there's a chance that it might have been "bugged". Usually copying that modified unit will cause the problem. AFAIK this problem started when the database was updated during the release of the Korean Missile Crisis.

I've started to notice this problem when I was working on my ship templates where if I copied a modified unit, the information on the sidebar will display the previous selected unit. Everything can still work even the edited attributes will work as intended (but won't display properly), but once you saved the scenario you can't access it again (thread title).

One way to simulate this problem is editing a simple unit. For example I'll use the Patriot SAM. Then I keep adding the M901 Launch Station to meet my needs, but if you add "too much" then you will soon face this bug.

Before the Korean Missile Crisis update, there was no problems about this. You could add as much weapons/sensors to a unit without facing this kind of problem.

Edit:
It seems that the current version of the DB doesn't face this problem anymore. I'm not exactly sure when was this problem "fixed" because I haven't touched CMANO in a while. However the problem did really happen during the KMC update and before the fix for this.



MorningDew -> RE: "Object reference not set to an instance of an object" (4/6/2017 1:23:55 PM)

When you say "The current version fo the database", I have the most recent version I believe (using steam). Is there a newer one?



Rain08 -> RE: "Object reference not set to an instance of an object" (4/6/2017 4:27:24 PM)

I'm assuming that's the reply to my edit. What I'm referring to as the "current" one is the DB3K 464 (SR7-B906.26).



ZoroastroBR -> RE: "Object reference not set to an instance of an object" (4/6/2017 4:45:23 PM)

I stand by what I said earlier about the Community Pack 34 working with the latest CMANO update while a few Community Pack 35 scenarios don't work. For example: H Hour from Northern Furry series and Closing the Kurile Gap from War that Never Was series.

I can't even open the scenarios using the editor (from CP 35).

I do have DB 3K 464 installed.



mikmykWS -> RE: "Object reference not set to an instance of an object" (4/6/2017 5:05:17 PM)

Hi Guys

Thanks for your reports.

Something is definitely up. We've had a non steam report so it may not be linked. I've added a ticket and sent some files in for our wizards to look at.

Thanks

Mike



Meroka37 -> RE: "Object reference not set to an instance of an object" (4/8/2017 8:50:21 AM)

I'm after this guys



michaelm75au -> RE: "Object reference not set to an instance of an object" (4/9/2017 1:44:11 PM)

It isn't every scenario in CP35, most of the ones I selected are loading okay. The stated 'Closing gap' ones fail for me too.



ComDev -> RE: "Object reference not set to an instance of an object" (4/10/2017 7:47:24 PM)

Hi guys, can you re-try this with the very latest exe. Are the scens loading correctly now?



ComDev -> RE: "Object reference not set to an instance of an object" (4/10/2017 7:57:14 PM)

Strike last, the files are corrupted. The bug that caused the corruption should now be fixed.

Thanks!



sergiopl -> RE: "Object reference not set to an instance of an object" (4/15/2017 3:16:49 PM)

It appears that the problem is not fixed yet. I´m using Build 936.2, and when I try to load several community scenarios (for example: Northern Fury 8) an error message appears, different from the previous one:

ERROR! The scenario is probably corrupted, could not determine which database to use!

[image]http://fotos.subefotos.com/b7641a93d26e4fc7b4bf1def76995bcfo.png[/image]

When I clic "Accept", the same message than before shows up (Object reference not set to an instance of an object)

Am I missing something?



mavfin -> RE: "Object reference not set to an instance of an object" (4/15/2017 4:01:31 PM)

If the problem is that some of the files are corrupted in the pack, then the scenario pack has not yet been fixed. The bug causing the corruption has been fixed, but not the corrupted files, unless I misunderstood.

Mav



sergiopl -> RE: "Object reference not set to an instance of an object" (4/15/2017 4:07:59 PM)

So... in that case what I would be "missing" is reading comprehension [:D]

Thanks!



mavfin -> RE: "Object reference not set to an instance of an object" (4/15/2017 4:44:57 PM)

Yeah, i get the same error with Northern Fury 8, and I'm using the Release Candidate B936.2.

I suspect the maintainer of the pack is scrambling around verifying all the files in the pack, and then finding good copies to update/rebuild the corrupt ones.

It'll take some time. That's a LOT of files.

Mav



mavfin -> RE: "Object reference not set to an instance of an object" (4/20/2017 3:55:37 AM)

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 -> RE: "Object reference not set to an instance of an object" (4/20/2017 4:15:36 AM)

Yes it's being taken care of.



Dimitris -> RE: "Object reference not set to an instance of an object" (4/20/2017 7:35:06 AM)

Fixed with release of updated community scenario pack.



Fer_Cabo -> RE: "Object reference not set to an instance of an object" (4/20/2017 8:02:25 AM)

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 -> RE: "Object reference not set to an instance of an object" (4/20/2017 10:24:41 AM)

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 -> RE: "Object reference not set to an instance of an object" (4/20/2017 8:57:34 PM)

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



chops -> RE: "Object reference not set to an instance of an object" (4/21/2017 1:55:05 AM)

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

Please see my post in the Tech Support Forum today.



mavfin -> RE: "Object reference not set to an instance of an object" (4/21/2017 2:38:02 AM)

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 -> RE: "Object reference not set to an instance of an object" (4/21/2017 5:34:25 AM)

quote:

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 -> RE: "Object reference not set to an instance of an object" (5/1/2017 10:44:32 AM)

Still no progress on this?



Page: [1] 2   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
3.613281E-02