[TWEAK B1009.27.5] After update to v1.15 Build 1009.27.3 can't update some scenario DBs

[AlexinCT]

While updating a few of my homemade scenarios, I have gotten the error in attached image (Ship #0 not found in DB). In an effort to find what the problem DB entry is I deleted one side after another in order to detect what side was the one with the issue only to end with a scenario without sides (basically blank) that after adding a new fake side, still produced the same error.

Wanted to upload the scenario for the devs, but keep getting an error that the type of file is not supported for uploads.

[AlexinCT]

Looks like the issue was that the file might have been too large so I zipped it.

[AlexinCT]

Nothing on this??

[RoryAndersonCDT]

You uploaded the .ini file not the .scen.

[AlexinCT]

Doh sorry. Here you go.

I have several scenarios I have made that throw this same error. Can't figure out what is causing some to update the DB with similar content and others not to.

[RoryAndersonCDT]

Its showing up here as DB3K 477 which is the latest DB?

[AlexinCT]

Sigh.

I apologize I loaded the wrong one. Confirmed this one does recreate the issue I reported though.

[RoryAndersonCDT]

I think you can ignore this error, are any ships missing after the DB update?

[AlexinCT]

Unfortunately I can't ignore the error because as you can see in the attachment in the first post, it terminates the migration process and tells me to contact the DB owner to correct the problem. This leaves me with several scenarios where I simply can't update the DB because of this error I can't seem to isolate or correct. If there is a way to force it to do the update anyway, I would like advice on how to accomplish that.

[RoryAndersonCDT]

Will discuss with team how best to fix this, perhaps this should just become a informative message and any units that aren't able to be updated should be deleted, and the update progresses without incident.

[AlexinCT]

As long as it tells you what the unit was that it couldn't update and was deleting, I would be fine with that rather than a scenario I can't update. I am familiar with the messages it provides after the update happens where unit loads for aircraft are not correct, and simply correct that. In this case if it told me it couldn't update a certain ship, I could just get the ship from the updated DB and reconfigure it.

As I mentioned when I reported the error however, in order to figure out what potential unit was causing the error when I first got it, I systematically deleted one side after another in the scenario, hoping that once the culprit side was gone, I could reload the full scenario and focus on the various units on that side until I found the culprit. But I ended up with a scenario that had nothing left in it (all sides were deleted), created a blank new side since I couldn't run the update without one, added nothing (basically a blank scenario), and the update still gave me that "Ship#0 not found" error.

[Dimitris]

I tested this now, with the current internal B1009.27.5 build. The only problem encountered was that a ship mount was problematic in being restored (did you make any mount customization?), so I added a "let it go and move on" bypass. After this it had no problem migrating to DB3K v477.

Please give this a go when B1009.27.5 is released and let us know.

[AlexinCT]

I did make quite a bit of customization, yes, so that explains it. Can you share what mount it was? Will help me try to avoid it or be better prepared.

And thanks for taking care of this.

[Dimitris]

If it helps you anyhow, it was the mount with UID: 461743d7-2614-4c0c-ab92-861b6c87ca3a , on the ship "PL 61 Hateruna #20856" (UID: da0ccf08-829d-4193-94d8-3faa489acfa5).

[AlexinCT]

Interesting. That ship you mention (PL 61 Hateruna), which is a Japanese Coast Guard ship, is NOT in this scenario at all.

Could you have linked the wrong unit from some other scenario to my request? Because if that is really the ship it is having an issue with when I ask it to upgrade the DB, I am unsure how that was found in the scenario.