Jump to content

Hang at load: "can't open Objects[us carrier tech] table"

Nealius

By Nealius
in Game Crash

 Share
Go to solution Solved by Nealius,

Recommended Posts

  • ED Team
maximov

maximov

Posted
  • ED Team
Posted
В 20.05.2023 в 10:20, Nealius сказал:

Still an issue with 2.8.5.40170. I am unable to play any paid Supercarrier campaigns that I have bought (Raven One, Fear the Bones, Speed and Angels) because of this app hang.

As I understand it, this problem occurred to you back in the game version 2.8.3
Paid campaigns do not depend on your placement of static units on the deck. That is, the problem is somewhere else. Do you have free space on the drive (or on another drive)? I suggest trying to install the game (additionally) in another folder. No need to install all your modules. Enough of the F-14 and the Supercarrier to launch the F-14A Fear the Bones campaign.

Nealius

Nealius

Posted
  • Author
Posted (edited)

New log after removing DCS.openbeta folder. This time the mission loaded, however it stopped at Sim PostStart for about 2 minutes, and there are still deck equipment table errors in the log, some of them repeated.

Before I install another instance I will try adding my Saved Games folders back to see if one is causing the issue.

 

New-dcs.log

Edited by Nealius
Nealius

Nealius

Posted
  • Author
Posted

Update: 

I removed my Saved Games/DCS.openbeta folder and returned my old folders one-by-one, except for a few folders like "Data" and such. 

So far I have not had the Sim PostStart hang after about 5 consecutive Supercarrier mission launches. I'll have to give it a few more days of flying to see if it comes back. 

Nealius

Nealius

Posted
  • Author
Posted

Yes to hangs on Fear the Bones. Haven't tried the other two yet. 

Creating a new mission has no change. It will work for a bit then after a while start hanging just like the old missions.

Nealius

Nealius

Posted
  • Author
Posted (edited)
1 hour ago, maximov said:

Could that be the problem?

I would expect the bug to return immediately after returning the folders if that were the case. The folders I returned were only those necessary:

Config, Liveries, Mission Editor (custom payloads), Missions, and related folders/files for VAICOM and Scratchpad. Minimum necessary for VR play. 

Update:

I'm experimenting and none of this seems to be making any sense. I ran "CVW-1 Afternoon" and it froze at Sim PostStart. I restarted DCS and tried the attached "Marianas Sandbox Afternoon" which has deck equipment but no deck crew, and that mission loaded successfully. I then tried "CVW-1 Afternoon" two more times, both times failed. So then I made two edits of "CVW-1 Afternoon:" one with deck crew but no carts/cranes, one with carts/cranes but no deck crew. Both loaded successfully. And now the original "CVW-1 Afternoon" mission loads successfully too. 

It's completely random. 

 

Marianas Sandbox Afternoon.miz CVW-1 Afternoon NoCarts.miz CVW-1 Afternoon NoCrew.miz

Edited by Nealius
Nealius

Nealius

Posted
  • Author
Posted (edited)

@maximov Similar as in just the Supercarrier+static objects, or everything including client slots, AI, waypoints, triggers, etc.?

As a related note, that day (30MAY) all Supercarrier missions loaded fine, although they would pause for a long time at Sim PostStart. The next day (31MAY) all Supercarrier missions would stop loading, still stuck at Sim PostStart for longer than 5 minutes. It almost seems like it's an incompatibility with my system or some software rather than an issue internal to DCS?

Edited by Nealius
  • ED Team
maximov

maximov

Posted
  • ED Team
Posted
6 часов назад, Nealius сказал:

Similar as in just the Supercarrier+static objects

If this condition is enough to make the mission hang, then of course it is better to create a simpler mission. If the mission does not hang when loading, then you can add additional elements.

Nealius

Nealius

Posted
  • Author
Posted

I hate double-posting but I found something interesting that works as a workaround. 

I created a Caucasus debug mission with static objects and deck crew on the super carrier. This mission does not crash at Sim PostStart--I do not know why.

If I run this debug mission and then run one of my bugged missions, the bugged missions run normally. If I do not run this debug mission, then my bugged missions crash as usual.

It's as if running this debug mission somehow clears the bug from DCS for that play session.

SuperCarrierDebug.miz

  • Like 1
Wiggo

Wiggo

Posted
Posted (edited)

I think I have the very same prob. With F/A-18c, even with DCS fully repaired, with extra file search and every mod taken off, I get freeze on loading window. I first thought it was "Sim poststart" problem, because that is what is on screen when the loading freezes (there is no way out it, only forcing windows to quit dcs gets me off that loading screen..)  That loading screen porblem was not the case when ppl looked my logs, in topic for that loading screen problem), but I was tipped that my log seem to tell it is this. For example, for now I cant start Raven One campaing AT ALL with my logbook. It SOMETIMES will start, if I remake /savedgames/dcs/missioneditor/ directory after and uninstall reinstall the campaign etc. It usually happens with persian gulf map, at least for me, but sometimes also in other maps. (Raven one is not the problem, it was just an example here, because that one triggers it everytime for me). I am not home now and cant reply the problem for logs, but I can do it later. My prob is always single player, with F/A-18c and ONLY has happened / replied / triggered with SP Hornet bought campaigs, usually, as mentioned, in PG map, but sometimes also with Caucasus. Maby it would happen with other maps too, if I used em more, or had bought campaings for ´em, really dunno.

Edited by Wiggo
Wiggo

Wiggo

Posted
Posted
On 6/6/2023 at 4:11 AM, Nealius said:

As of today above workaround of running Caucasus mission no longer works.

Yes it seems so. Me myself for example, cant start Raven One campaign AT ALL. None of before used workarounds havent helped anymore. Not even new logbook / remaking /savedgames/dcs/missioneditor folder. Before there was random workarounds, but not anymore. (I think this is not raven one campaings fault by any means!) Its sucks totally that I cant use campaings what I have payed for, but thats ofc another case. This prob is weird, because whole spring it has gone more and more usual and more and more worse, among updates. 😛

  • Like 1
Flappie

Flappie

Posted
Posted
On 5/24/2023 at 11:12 AM, Nealius said:

If I create a new mission for debugging, the "can't open objects[us carrier tech]table" errors appear in the log but they do not cause an app hang, and the mission loads normally.

It just occured to me that I also get this message in my logs, although missions don't hang on my PC.

Maybe the problem happens right after the "ERROR   wInfo (Main): can't open Objects[us carrier tech] table" line(s). Let's see: 

2023-06-08 19:49:55.188 ERROR   wInfo (Main): can't open Objects[AS32-31A] table
2023-06-08 19:49:55.188 ERROR   wInfo (Main): can't open Objects[CV_59_H60] table
2023-06-08 19:49:55.190 ERROR   wInfo (Main): can't open Objects[us carrier tech] table
2023-06-08 19:49:55.739 WARNING LOG (2420): 21 duplicate message(s) skipped.
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:initScript
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnCoalition neutrals
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnCoalition red
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnPlanes 27
2023-06-08 19:49:55.824 INFO    APP (Main): MissionSpawn:spawnCoalition blue
2023-06-08 19:49:55.824 INFO    APP (Main): MissionSpawn:spawnPlanes 2

I'm now pretty sure that the problem comes wen "MissionSpawn:initScript" is initiated. We need more detailed logs.

Can you please try this autoexec.cfg file? You need to save it in your "Saved Games/DCS.../Config" folder.

Then attach your dcs.log the next time you get the app hang.

autoexec.cfg

  • Thanks 1

---

Wiggo

Wiggo

Posted
Posted
On 6/8/2023 at 11:36 PM, Flappie said:

It just occured to me that I also get this message in my logs, although missions don't hang on my PC.

Maybe the problem happens right after the "ERROR   wInfo (Main): can't open Objects[us carrier tech] table" line(s). Let's see: 

2023-06-08 19:49:55.188 ERROR   wInfo (Main): can't open Objects[AS32-31A] table
2023-06-08 19:49:55.188 ERROR   wInfo (Main): can't open Objects[CV_59_H60] table
2023-06-08 19:49:55.190 ERROR   wInfo (Main): can't open Objects[us carrier tech] table
2023-06-08 19:49:55.739 WARNING LOG (2420): 21 duplicate message(s) skipped.
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:initScript
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnCoalition neutrals
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnCoalition red
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnPlanes 27
2023-06-08 19:49:55.824 INFO    APP (Main): MissionSpawn:spawnCoalition blue
2023-06-08 19:49:55.824 INFO    APP (Main): MissionSpawn:spawnPlanes 2

I'm now pretty sure that the problem comes wen "MissionSpawn:initScript" is initiated. We need more detailed logs.

Can you please try this autoexec.cfg file? You need to save it in your "Saved Games/DCS.../Config" folder.

Then attach your dcs.log the next time you get the app hang.

autoexec.cfg 56 B · 3 downloads

Downloaded and put to folder. I will pass you the files when next time freeze. Maby I´ll zip or something whole msneditor folder and dcs.log . Lets see.. 

Wiggo

Wiggo

Posted
Posted (edited)
On 6/8/2023 at 11:36 PM, Flappie said:

It just occured to me that I also get this message in my logs, although missions don't hang on my PC.

Maybe the problem happens right after the "ERROR   wInfo (Main): can't open Objects[us carrier tech] table" line(s). Let's see: 

2023-06-08 19:49:55.188 ERROR   wInfo (Main): can't open Objects[AS32-31A] table
2023-06-08 19:49:55.188 ERROR   wInfo (Main): can't open Objects[CV_59_H60] table
2023-06-08 19:49:55.190 ERROR   wInfo (Main): can't open Objects[us carrier tech] table
2023-06-08 19:49:55.739 WARNING LOG (2420): 21 duplicate message(s) skipped.
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:initScript
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnCoalition neutrals
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnCoalition red
2023-06-08 19:49:55.739 INFO    APP (Main): MissionSpawn:spawnPlanes 27
2023-06-08 19:49:55.824 INFO    APP (Main): MissionSpawn:spawnCoalition blue
2023-06-08 19:49:55.824 INFO    APP (Main): MissionSpawn:spawnPlanes 2

I'm now pretty sure that the problem comes wen "MissionSpawn:initScript" is initiated. We need more detailed logs.

Can you please try this autoexec.cfg file? You need to save it in your "Saved Games/DCS.../Config" folder.

Then attach your dcs.log the next time you get the app hang.

autoexec.cfg 56 B · 4 downloads

 

dcs.log

MissionEditor.rar

Edited by Wiggo
Flappie

Flappie

Posted
Posted

Thank you, @Wiggo. Unforunately, detailed log don't show much more. It still ends with: 

2023-06-09 22:45:25.119 ERROR   wInfo (Main): can't open Objects[Carrier LSO Personell 2] table
2023-06-09 22:45:25.120 ERROR   wInfo (Main): can't open Objects[Carrier LSO Personell 3] table
2023-06-09 22:45:25.121 ERROR   wInfo (Main): can't open Objects[AS32-36A] table
2023-06-09 22:45:25.121 ERROR   wInfo (Main): can't open Objects[us carrier tech] table

As for the MissionEditor folder, I don't see anything wrong. I replaced mine with yours, then I ran some Fear the Bones! missions as well as the Sandbox mission, without any issue.

I enabled detailed logs on my PC to see if I could find anything new, but nope. 

2023-06-09 23:20:17.987 ERROR   wInfo (Main): can't open Objects[CV_59_Large_Forklift] table
2023-06-09 23:20:18.002 ERROR   wInfo (Main): can't open Objects[us carrier tech] table
2023-06-09 23:20:18.002 ERROR   wInfo (Main): can't open Objects[AS32-p25] table
2023-06-09 23:20:18.018 ERROR   wInfo (Main): can't open Objects[us carrier tech] table
2023-06-09 23:20:18.018 ERROR   wInfo (Main): can't open Objects[CV_59_H60] table
2023-06-09 23:20:18.033 ERROR   wInfo (Main): can't open Objects[CV_59_MD3] table
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:initScript
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:spawnCoalition neutrals
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:spawnCoalition red
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:spawnPlanes 0
2023-06-09 23:20:18.215 INFO    APP (Main): MissionSpawn:spawnVehicles 0

 

  • Thanks 1

---

Wiggo

Wiggo

Posted
Posted (edited)
12 hours ago, Flappie said:

Thank you, @Wiggo. Unforunately, detailed log don't show much more. It still ends with: 

2023-06-09 22:45:25.119 ERROR   wInfo (Main): can't open Objects[Carrier LSO Personell 2] table
2023-06-09 22:45:25.120 ERROR   wInfo (Main): can't open Objects[Carrier LSO Personell 3] table
2023-06-09 22:45:25.121 ERROR   wInfo (Main): can't open Objects[AS32-36A] table
2023-06-09 22:45:25.121 ERROR   wInfo (Main): can't open Objects[us carrier tech] table

As for the MissionEditor folder, I don't see anything wrong. I replaced mine with yours, then I ran some Fear the Bones! missions as well as the Sandbox mission, without any issue.

I enabled detailed logs on my PC to see if I could find anything new, but nope. 

2023-06-09 23:20:17.987 ERROR   wInfo (Main): can't open Objects[CV_59_Large_Forklift] table
2023-06-09 23:20:18.002 ERROR   wInfo (Main): can't open Objects[us carrier tech] table
2023-06-09 23:20:18.002 ERROR   wInfo (Main): can't open Objects[AS32-p25] table
2023-06-09 23:20:18.018 ERROR   wInfo (Main): can't open Objects[us carrier tech] table
2023-06-09 23:20:18.018 ERROR   wInfo (Main): can't open Objects[CV_59_H60] table
2023-06-09 23:20:18.033 ERROR   wInfo (Main): can't open Objects[CV_59_MD3] table
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:initScript
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:spawnCoalition neutrals
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:spawnCoalition red
2023-06-09 23:20:18.120 INFO    APP (Main): MissionSpawn:spawnPlanes 0
2023-06-09 23:20:18.215 INFO    APP (Main): MissionSpawn:spawnVehicles 0

 

Ok. Weird. I did not get replied the problem yesterday anymore, with any other campaing, than Raven One. I will try today re-install the campaing, and restart it, and then try again. Is the end of the log the point where it freezes  or the point where I force dcs.exe down... (there is no other way out, I waited for many minutes yesterday before forcing dcs down). I could of also try to let it be in that window longer, but computer really seems to be doing nothing after the freeze, as the reading from drives end (thoug process still takes alot of power from computer, dunno really what is going on there.) I have pretty old computer, but clearly there has been no problems with it ever while playing. (i5 4960k+ 20gb ddr3 +gtx 960 4gb). Maby re-install dcs, but thats PAIN with my internet connection. And actually I re-installed DCS some time ago as I bought new ssd. The prob was also with install before it. But still, I will just let it be and see what happens with re-installing the campaing, cause clearly the problem replies with that very campaing. Btw I get also script errors in Operation Pontus campaing, everytime when I destroy something, just thought I will mention that if it has something to do with this. I think not, but just mentioning. But yeah, thanks for checking that MissionEd. folder. I had some weirdomobs before (couple of months ago) but I think it is more or less in condition now. I can report if I somehow get it working. Seems weird that it is just with one campaing, and no errors. Thanks alot though! 

BTW: Should I remove that autoexec file? What does it even do? (just for interest, maby learn something some day, as mentioned pretty new with dcs, but not with computers or gaming.) 

Edited by Wiggo
Flappie

Flappie

Posted
Posted

I have an idea. You should use Windows Resource Monitor to check which files are being accessed when the freeze happens.

  1. Run it before starting DCS, select the Disk tab, start DCS, then tick "dcs.exe" in the top part of the Disk tab. All files listed in the bottom part are files accessed by DCS. They disappear after some time when DCS don't access them anymore.
  2. From the moment you run the mission, Alt+Tab and take a screenshots of the Resource Monitor screen, until the file list does not change anymore, then attach them here.

 

---

 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...