Graphical and crashing issues on FireStarter 2004 by gsc game world about d3d8to9

[elishacloud]

@LethalManBoob, you mentioned here that this last fix "now works perfectly on serious sam first encounter and firestarter." Does that mean that this issue is fixed? Can we close this issue?

[elishacloud]

@LethalManBoob,

1. Is this issue related to the reg fast_load INT "1" mentioned in Cant use Driver Forced AA?

2. Can you give me more details about your system? Operating System, graphics card, etc. I am seeing weird issues even without d3d8to9, so I am wondering if this is an issue with the game.

3. Also, are you using the GOG version of the game or some other version?

4. Can you upload the log files from the game?

[LethalManBoob]

As far as im aware its a completely separate issue. I use the latest windows 10 with a gtx 1080 and an i7 6700k with 32gb ram and no i dont have stupid bloatware or anything. I keep my system clean. I never crashed when using fast load 1 without d3d8tod3d9 but i did loose things like fog. With d3d8tod3d9 i get frequent bad random garbage polygons and eventual crashes. Thankfully the only issue i ever had with d3d8tod3d9 on with fast load 0 is that the tv monitors flicker. Thats it really. Oh and yes I use the gog version.

…

On 13 November 2017 at 04:59, Elisha Riedlinger ***@***.***> wrote: @LethalManBoob <https://github.com/lethalmanboob>, 1. Is this issue related to the reg fast_load INT "1" mentioned in Cant use Driver Forced AA <#54 (comment)>? 2. Can you give me more details about your system? Operating System, graphics card, etc. I am seeing weird issues even without d3d8to9, so I am wondering if this is an issue with the game. 3. Also, are you using the GOG version of the game or some other version? 4. Can you upload the log files from the game? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#49 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ac3uuznKJXdDWtwB89iIb7cYdmiUspP3ks5s18y5gaJpZM4PdBn_> .

[elishacloud]

How do you set fast load 1? Is this a game option? Can you give me more details on how to configure this?

[LethalManBoob]

Its in your BASE folder as env_vars.cfg

…

On 21 November 2017 at 19:03, Elisha Riedlinger ***@***.***> wrote: How do you set fast load 1? Is this a game option? Can you give me more details on how to configure this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#49 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ac3uu3cvq3hiD3JYTCfmdTmohV0VmCoLks5s4x6HgaJpZM4PdBn_> .

[LethalManBoob]

Alright scratch that. While serious sam tfe still is fine. Firestarter and tse arn't.

[elishacloud]

@LethalManBoob, I did not understand your response. What issues are remaining in Firestarter? If the only issue is with MSAA then we can close this issue since the MSAA issue is tracked in #63.

Please let me know if you are still experiencing other issues with d3d8to9 besides MSAA in Firestarter.

[LethalManBoob]

Well firestarter has random crashes to desktop and the monitors in game flicker when using the module. I also reported random polygon corruption and stretching on earlier d3d8.dlls

As a note i have never had a single crash or artifact until using the module. Completely repeatable.

[elishacloud]

@LethalManBoob, I am not seeing any issues here with the latest updates. Can you try with this build: d3d8.zip

[LethalManBoob]

Monitors still flicker a little but it is much less noticeable and all other aforementioned issues have been seemingly fixed.

[elishacloud]

Thanks @LethalManBoob. Looks like the latest pull request (#108) fixes this game also.