Crossfire - Upcoming changes, upcoming content

patch is out

You can activate the new renderer via the launcher options (shader option menu)

As already mentioned the patch is pretty big ~4,5gb (about 3,5gb disc space). Lots of stuff has changes with this update since pretty much all 3d models have been edited.

Various 3d models got retextured, some even remodeled (the majority of these changes also apply to the DX version).

There are a few minor issues as described above. I can fix most of them but required to know where lighting errors happen (exact location - if possible with screenshot).

The server also got patched (a requirement to keep the anticheat from banning everyone). I hope that everything went well and it remains stable (could not test it prior release).

transparent?

from what I can see is that the detailmap of the terrain is different (because the renderer can not correctly deal with that yet) and the lighting is different

as mentioned not all parts already use the full feature set of the new renderer (NPC + cutscenes + station interiors, static asteriods)

Maybe one more thing to mention:

There are two new functions you can assign keys to on the game options. There is a OpenGL option menu and a Dev menu. You can freely assing keys to open them.

However, atm the changes done there won't save. They will reset with the next launcher update. I will fix that later.

most certainly not related to the update

it does not change anything that could cause that but Ive updated a plugin recently which is active in MP

Need to observe it a bit

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.

any logs?

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.

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.