Crossfire + Windows 10 build 1809

I can not allow that but I probably can also not prevent you from doing that.

no suggestions unfortunatly since i dont understand how this error still could happen eventhough the source of the error was bypassed

maybe we can do a teamviewer session so I can investigate on this issue on your PC?

I can not reproduce it on my PC.

I had a Teamview session yesterday evening with a player that had problems getting Crossfire to work.

A good opportunity to see the problem from a different perspective.

I think there are 3 key issues that could lead to problems.

1. A disabled DirectPlay in Windows 10.
   Windows 10 by default has this feature disabled (god knows why).
   Here you can read how to enable it: How to Enable the Ultimate Performance Power Plan in Windows 10
2. The next common problem is when the game is getting installed into the "C:\Program Files x86\... " directory.
   This could lead to user permission issues.
   It is much better to install the game into the root directory of a HDD/SSD -> e.g. "C:\Freelancer\"
3. And finally Windows 10 build 1809 is an issue due to the changes that were done to the DirectX functions of that build.
   The workaround that I created bypasses these functions and allows the mod to run at least under the Vanilla FL shader setting until I can provide a better fix.
   However, yesterday I noticed a minor issue in which the workaround did not apply instantly. I got it to work but it took additional steps.
   Not a big deal actually but uncomfortable especially for players which install the mod the very first time.
   Thats why I changed a few default settings. Now the workaround should apply on the first try (especially for new players).
   The instruction how to apply this workaround remain the same.

Sometimes a different perspective helps to see the issues more clearly.

After a few hundred tests on vanilla FL it looks like I have a working solution.... at least for one of the settings so far. No crashes with active shaders under Windows 10 version 1809.

Ill try to apply this to the other available settings tomorrow.

Depending on the results I might have to completely rebuild the shader options on the launcher (my current solution is working somewhat different than the options before) or I might add a compatibility option. Dunno yet.

It also might be worth testing that stuff on older windows versions prior releasing it.

Thats a huge step into the right direction.

hmmk

I have multiple working solutions now for enb, sweetfx and reshade.

Most likely it will be best to completely rebuild the shader options since my solutions work totally different from what we used before.

I can imagine having more fixed options that offer various settings.

On top of that I would provide one option that renders the game in dx10 instead of just dx8/dx9 and allows players to do custom shader settings in the game.

Most players might stick with the default options but for some the custom shader option might be a very interesting alternative.

It might take a few days to write new config files and try to figure out how to distribute that shader update.

The update will most likely be released tomorrow afternoon/evening.

I still need a few hours preparing the update process since everything became a bit bigger and more complex in the end.

391 files - 36mb

3 enb shader variations

11 SweetFx+Reshade variations

1 Rehade on dx10 which is fully customizable (you can create and store your own presets in the game)

Vanilla FL

ENB Default

ENB Oversaturated

ENB MotionBlur + Sharpen

RS+SFX SMAA Min

RS+SFX FXAA Min

RS+SFX SMAA Default

RS+SFX FXAA Default

RS+SFX SMAA Full

RS+SFX FXAA Full

RS+SFX MotionFocus

RS+SFX Emboss

RS+SFX Filmic

RS+SFX 8mm

RS+SFX VHS

Reshade DX10

I tried to keep the controls as similar as possible but that did not 100% work.

ENB activation is via Shift+F12

RS+SFX activation is F12

The Dx10 Reshade also is F12 while the config menu can be accessed via F11. It also should be the most resource intense version but it provides the most customization options.

I also noticed that all the intro videos are playing correctly now but I am not sure if that is a positive side effect from the new shaders or if there is some windows setting that I did which now is causing the vids to play without black overlay.

The vanilla shader option is exactly the same as the one we had prior this update. I see no way how (especially this option) could lead to such problems.

Maybe a restart of the PC would help... dunno.

actually sounds ok... except the black screen

if one shader does not work for you... select a different one

they use different methods and most likely not all are supported by every graphic card.