Pike13 Posted February 28, 2018 Share Posted February 28, 2018 With the latest 2.64 I'm encountering an error the second and subsequent times I attempt to launch a PBFX2 table. First time: no problems. The error I receive is: Launching PBFX2 directly before or after the problem works fine. Exiting PinballX and relaunching works as well (the first time only). Going back to 2.50 works fine as well. I installed the latest NVIDIA drivers and installed DirectX again. DXDiag indicates no problems. No Application errors in the Windows event log. Attached my log.txt file and PinballX.ini files. Any ideers? log.txt PinballX.ini Link to comment Share on other sites More sharing options...
Outhere Posted February 28, 2018 Share Posted February 28, 2018 Tom must be working on it Link to comment Share on other sites More sharing options...
Tom Speirs Posted February 28, 2018 Share Posted February 28, 2018 Best just to roll back to 2.50 for now. I'm offering it as default. 2.64 has quite a few issues I need to address. Link to comment Share on other sites More sharing options...
funkyman Posted March 1, 2018 Share Posted March 1, 2018 Quote Best just to roll back to 2.50 for now. I'm offering it as default. 2.64 has quite a few issues I need to address. I figured that's why you rolled back versions. I've been testing/running on the "2.64 leak patch" you sent me (everyday since then) and it's been working great, no issues. However, I'm only using Visual Pinball 9/10 tables. I wonder if it's because of the Video Card / DirectX combo or just lucky since I didn't try anything fancy Either way, thanks for the work you put in! Link to comment Share on other sites More sharing options...
Tom Speirs Posted March 1, 2018 Share Posted March 1, 2018 No worries. Obviously as usual the project is in active development so I will get to it soon but yes there seem to be some directx conflicts for some setups. It works fins for me too but I am a bit behind also. Link to comment Share on other sites More sharing options...
Pike13 Posted March 4, 2018 Author Share Posted March 4, 2018 2.65 seems to have fixed the issue. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts