Posts by SWAT_OP-R8R

That is not going to be as easy as you might hope it would be.

I don't know your starting point (if you maybe already know which 3d model file is used or not)... but let's just assume you know (I don't).

In shiparch.ini you will find all ship definitions including stats. There you can search for the file name of the 3d model to find the nickname of the ship_archetype.

Before you shout "hurray"... you can not use it for editing a savegame (I assume that is what you want to do).

Instead you have to figure out if this ship nickname has been used to create a playable ship already. If so you can find the nickname from the shiparch.ini somewhere in the goods.ini labled as a ship package. Copy this ship package name... and search for it in the same goods.ini file. You should find a ship definition with a loadout (engines, powerplant, etc) then. The nickname of this ship definition is what you need for your savegame.

However, in order to use it in the savegame you will have to convert it to a crc using FLdev or CRCtoolkit or probably a million other tools able to do that task.

the last update has not changed anything other than adding the new renderer

if it was working before it should also work now (if you select the old dx shader options)

The celestis should now be fully working with the new texture set.

from an account that was just created today?

?

Quote from <SF>IndianaJones

Same effect for me, same effect if i try to switch to my celestis dreadnaught.

Just took a quick look at vogtland base and can confirm the crash.

An initial test seems to indicate an issue with the celestis dreadnaught texture files which cause this crash. I reverted the opengl changes for this ship (partly) so the base and the ship are no longer crashing but I dont exactly know the error yet. Maybe I will find time later next week to provide a fully working fix.

For now this band aid patch has to suffice.

Ticket

Will do that later.

I did a bit research on the issues shown in the vids.

The detailmaps on planet sprague seem to work correctly in opengl but the lighting is way too bright causing the visual issues. This can be fixed later on but needs a more complex setup.

Detailmaps however seem to be an issue on 73 station rooms where a specific kind of detailmap is used. I can edit these rooms to use a different method of applying detailmaps but that will take some time and it might have side effects such as darker textures. This probably can be compensated with additional light sources and new scripts for the opengl version.

Lots of work... and ~1,3 gb of additional patch size.

In the end the key message is "it can be fixed but will take time".

edit:

Why this specific type of detailmap is not working correctly is not known to me. Maybe there is a specific reason for it or maybe it was just an oversight. I will try to get the information first before editing all the assets.

any crash logs similar to eventviewer available?

you fly next to it and it will do the job

Does the same issue happen with opensp or mp?

witchcraft

I was thinking about more detailed logs.

How to get started with Event Viewer on Windows 11 | Windows Central

evenviewer should have entries for Freelancer right at the time when the crash happens.

You can replay the last vanilla mission an continue from there.

any logs?

F12 is the Reshade activation buttion

It might be that you have a preset active which applies a shader that causes what you describe. You can check it by pressing the "home" button.

I dont think that this is related to the OpenGL Renderer.

I just last night tested some shader options and noticed that the Dx10 recommended option caused crashes. I am not sure if this is related to the latest reshade version or what else might cause it. Uppon shader compilation it crashes at a windows internal function.

I can not tell if this is a general issue or if this is related to certain hardware yet. For now this shader option is renamed to dx10 (v1)... while the DX10 (v2) option has been made the default selection. If you use something different you will have to do the setttings again in the launcher options.

The V2 option seems to run stable.

Also that one texture bug in the logs above got fixed.

The download error is something I can fix later this day.

The crash however is strange.

That error message in the image is something I have never seen before but I found it reported once in a different mod back in 2006.

The suggested solution was to reinstall because model geometry might be missing for some reason.