OSE WiP V0.4 & Oolite trunk RVN 2188 - partially FIXED

[Lestradae]

I'm sorry that I have to report that the Crashy Dredger still inexplicably crashes with the "1.73" trunk build, revision I think is SVN 2193 from today, half an hour ago version.

Used OSE WiP V0.4 which again gave me the exact same error message in the log as with the Crashy Dredgers testcase oxp, crash to desktop when the picture of a Dredger appeared while looking at the shipyard (F3-F3).

The Dredger model didn't even turn, the whole screen froze and then crash to desktop. At the end, again, the usual, dreaded Log message:

[ship.escortSetup.wtf]: Pending escort count for <ShipEntity 0x9762c78>{"Deep Space Dredger Courier" ID: 266 position: (683.047, 455.365, 3642.92) scanClass: CLASS_NO_DRAW status: STATUS_COCKPIT_DISPLAY} is 8, expected 0. This is an internal error, please report it.

As there is nothing wrong with the Dredger model or the shipdata plist - works fine under 1.72.2 - this must showcase a bug somewhere in the trunk build. Hope my observations help nailing it down ...



L

[Screet]

I'm sorry that I have to report that the Crashy Dredger still inexplicably crashes with the "1.73" trunk build, revision I think is SVN 2193 from today, half an hour ago version.

Argh. I really tried with Vista 64, XP 32 and XP 64 and could not reproduce that. Furthermore, since the fix for the exception-messages in stderr cause I didn't have oolite crash a single time.

This sounds like a really difficult problem...

Screet

[another_commander]

Here is the Crashy Dredger from the shipyard on my trunk version (latest of which happens to be 2196, not 2193). Nothing wrong with it here.

If you have a different way to reproduce, please let me know, otherwise I have to assume it is something to do with your setup. The Crashy Dredger test case simply works for me.

[Lestradae]

Argh indeed.

The good news: It's working on all your systems

The bad news: I would have started to develop OSE for 1.73 already, but only on my personal system the damn thing crashes

I have no idea at all what the difference is. The only oxps I had in were OSE WiP V0.4, my personal keyboard & sound configurations and my maxxed-out System Redux. None of the other oxps crash the game to desktop.

And the setup was a completely brandnew, clean installation of the trunk.

I'll wait and see. Thanks for looking into the issue atm

EDIT: Wait a moment. That my be an idiotic idea, but I read something about where the AddOns folder goes in the trunk. Can you tell me again where I have to put the AddOns folder under "1.73"?

[another_commander]

Under Windows, the AddOns location remains as it has always been. This is the case if you are building from the instructions at the sticky thread on the PC subforum and will be the same for the final release.

[Screet]

EDIT: Wait a moment. That my be an idiotic idea, but I read something about where the AddOns folder goes in the trunk. Can you tell me again where I have to put the AddOns folder under "1.73"?

If you're talking about the build environment, it's the "trunk" folder which contains the subfolder "oolite.app".

However, if you create an installer, it's the Oolite folder which contains "oolite.app".

Screet

[Diziet Sma]

More precisely, if you build from another_commander's sticky, they're in the standard locations, as he says above.

If you build from the wiki instructions, it depends on how you launch the game.

If you launch the game using the GNUstep shell, as described in the Wiki, with the command "openapp oolite.app" then AddOns will need to be in "C:\GNUstep\Local\oolite" and gamesaves will be in "C:\GNUstep\Local\oolite\trunk"

If, instead, you go into the "C:\GNUstep\Local\oolite\trunkoolite.app" folder and launch the game directly, by clicking on the executable, then all folders will be in their default locations.

See here for the gory and embarrassing details of how I figured this out.

What I now do is, after creating a new build using the Wiki directions, I move the entire newly-created oolite .app folder to a special location, "C:\Oolite trunk\oolite.app" and I also created a Start-Menu shortcut to the executable at that location, to launch the game. That way I can replace the oolite.app folder with a new build easily, and the AddOns and game-saves I use in testing will still be there (and in the standard locations). Additionally, the shortcut will continue to work when I change to a new build, so now I have one-click launching of Trunk, no matter how often I update it.

[Lestradae]

A new and not very helpful development.

After getting this escort line in the log after crashing, I took any and all escort entries out from the crashy Dredgers shipdata plist.

And guess what? Having a Dredger drawn on any picture still crashes the game to desktop - but there is now no problematic entry in the log at all.

Whoever gets this shall, I don't. Especially as this seems to be working on everybody else's system but mine.

Can someone make me an installer for trunk 1.73 and send it to me, please? Just to be sure I didn't do something funny to my installation following A_C's short instructions. Thanks.

Still

L

[Screet]

Can someone make me an installer for trunk 1.73 and send it to me, please? Just to be sure I didn't do something funny to my installation following A_C's short instructions. Thanks.

I'll send you one in a few minutes!

I have another idea...could it be a problem with the graphics driver, which somehow only happens with the new trunk graphics features?

Maybe it's different if you switch to wireframe or shaders off?

Screet

[Lestradae]

I have another idea...could it be a problem with the graphics driver, which somehow only happens with the new trunk graphics features?

Ha! At last! Screet, you're brilliant - now we're on to something.

OK, so I tried out to switch off the shaders completely - and guess what, the Crashy Dredgers no longer crash my system!

It gets more weird, though. After loading a player-owned Dredger and changing the settings to shaders: full while in flight, no crash!

My graphics card: NVIDIA GeForce 8600M GT

So, how do I solve the $/&%$/& graphics driver issue? Is this a known problem after all?

[Screet]

My graphics card: NVIDIA GeForce 8600M GT

So, how do I solve the $/&%$/& graphics driver issue? Is this a known problem after all?

I'm not sure if Oolite can really enable shaders during gameplay, so maybe it just didn't crash because it continued with shaders off while in flight?

My card is a GTX295 with this driver: 185.85_desktop_winvista_64bit_english_whql.exe

However, I also did not have driver problems with my old 32bit Vista installation - but maybe something changed with the latest OSE beta or the drivers?

nVidia also has new beta drivers out - the release version should follow in a few days. Maybe the beta ones are worth a try for you?

I did send you an executable of my trunk build - not the whole installer, due to it's size problem. However, I doubt that it'll change that dredger experience.

You could try it though, I've some code in which should massively reduce kamikaze ships and I did build with turrets targeting missiles enabled

Screet

[Cows]

Where do you find the files for 1.73.
I compiled something from source, started it and realized I installed 1.72.2 all over again!

[Screet]

Where do you find the files for 1.73.
I compiled something from source, started it and realized I installed 1.72.2 all over again!

Sounds like you did not get the current source via svn? Have a look at this thread: https://bb.oolite.space/viewtopic.php?t=5943

Screet