[Bug 39586] Fallout 4 - Steam Version - Crash on Start-up

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=39586

--- Comment #21 from Kimmo Myllyvirta <kimmo.myllyvirta at gmail.com> ---
Created attachment 57771
  --> https://bugs.winehq.org/attachment.cgi?id=57771
wine-2.4 backtraces

While waiting for 2.5-staging, I'll post results with 2.4-staging.
With the now implemented CSGet* funcs the game goes a bit further, but still
won't start a new game.

The attachment is not very useful, as the exceptions happen inside the fallout4
and godrayslib, hunting these down was a bit difficult. But, in 1st backtrace
the problem is failing CreatePixelShader;
fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0xcc,
opcode_token 0x070000cc.
Recognizing the eval_sample_index (0xcc) is enough to fix this one.

When that is fixed, it starts hitting the missing hull/domain shader
implementation. 2nd backtrace (0xdead0002 comes from me setting the *shader to
that in HSGetShader). Pinpointing single failures is a bit pointless atm. The
game uses (currently unimplemented) tessellation for the god rays.

This can be tested with (this is also a workaround);
In the launcher options select any preset (low, ultra, doesn't matter), goto
Advanced settings and set "Godrays Quality" to "Off (best performance)".
Or alternatively change "bVolumetricLightingEnable=1" to 0 from
Fallout4Prefs.ini.
If you use the above settings a new game starts ok. (None of these will fix the
intro video for people having problems with it, I don't have an idea what's
wrong with it yet.)

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.