the reference to d3dramp.dll was removed from d3dim.dll in the 3.1 version (yet d3dramp.dll is still present on the system and keeps getting updated version numbers for some reason). While trying to determine what changed between the two versions, I found that e.g. If you can get a hold of an older version, that could be an alternative fix when not using a wrapper. The last working version of d3dim.dll is 4.1 and the first broken one is 3.1. I did some further digging and it looks like the ramp device is broken since the Windows 10 October 2018 Update. Hopefully it will be ready sometime during the upcoming week.īattles should also work now in full screen mode in the latest experimental release. Meanwhile, I'm working on fixing this and some other issues in DDrawCompat also. Though I wouldn't recommend this as a permanent solution, as mixing different system dll versions is likely to create other problems. In fact, I tried copying an older version of d3dim.dll into the game folder from both an earlier Windows 10 version and even from my Windows 8 system, and both of them fixed the issue. Like many users suspected on various forums, it seems that this was actually broken during one of the Windows 10 updates. I think it should work with other versions of the game also. It fixes the issue with the GOG version for me, even when just running the game natively without any ddraw wrappers. So this will force the game to use the RGB software emulation device instead of the Ramp software emulation device that it normally uses. These values are actually the GUIDs for IID_IDirect3DRampDevice and IID_IDirect3DRGBDevice, respectively. Using a hex editor, replace the following hexadecimal bytes in REBEXE.EXE:Ģ0 6b 08 f2 9f 25 cf 11 a3 1a 00 aa 00 b9 33 56Ħ0 5c 66 a4 73 26 cf 11 a3 1a 00 aa 00 b9 33 56 Reply to this email directly, view it on GitHub, or unsubscribe.įor those who are using Windows 10 and are only having trouble with graphical issues in the manual battle scenes, here's a possible solution. You are receiving this because you commented. I don't know when I'll get around to it, but I'll try to fix it for v0.3.0 eventually. Works fine with v0.2.1 as you said except for space battles (probably a palette issue since I did see an oddly colored ship for a short while.) Currently the game does not even start up with that.
I don't maintain older versions, so I'll have to look into what's wrong with the experimental release and fix that. Thanks, but I do actually have the GOG version already, I just haven't had time to look into this much yet. Subject: Re: Star Wars Rebellion - Cinematics are not displayed ( #22)
0 kommentar(er)
