-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arx Fatalis does not boot. #205
Comments
I got the game to boot with the latest update I just checked in. However, this game uses |
Does this render some objects invisible? |
Quick question, where are you seeing the rendertarget? |
rendertarget is a function that the game is calling. See code here.
It depends on what you want to do. But at this point the only settings in the ini file that would work would be |
im trying to determine the render targets for my rtx remix projects. I will try those functions now |
after enabling |
If you are trying to use RTX Remix then you will need to enable However, as I mentioned before the SetRenderTarget() code in dxwrapper is not fully implemented so it is not able to fully convert all of this game to Direct3D9. If you remark out these lines and recompile the code then you can get the game to load up. However, it will have issues because remarking those lines out just disables SetRenderTarget(), which is required by this game. |
Ahh I see! I am using a specific version of Arx Libertatis to use for RTX remix but have been running into a problem where the interactable objects do not render. RTX remix currently only points to render target 0 so I was trying to find out which other render targets the application points to. |
As far as I know, DirectX 7 games (like Arx Fatalis) only use render target 0. For Arx Libertatis, I am not sure what the solution is. Dxwrapper has a DirectX 9 wrapper, but it is not able to convert all the render targets to 0. It seems like it would take a lot of effort to covert a game from using multiple render targets to using only one. You could use dxwrapper to log which Direct3D 9 render targets are used by adding some logging here. Just enable the |
Oh! Amazing! Thanks for your help by the way. Greatly appreciated. |
I put an update in that allows Arx Fatalis to run without any code changes. It is still not playable as it has corrupt graphics on the main menu, at least it can start now. |
Oh, amazing. Thanks, I will try it when I get home tonight. |
With the latest build if you enable the below settings the game is getting close to being playable, but still has a lot of graphical anomalies. [Compatibility]
Dd7to9 = 1
[d3d9]
FullscreenWindowMode = 1 |
wow, that is awesome. I have not had a chance to run this yet but will test as soon as I can. |
Hi there. I just wanted to apologise as I have not had a chance to actually take a look at the changes for this. |
No problem. Here is the latest build to test with. The game is still not playable, but it is further along. Here is the test build: dxwrapper.zip |
The game is playable with the latest build if you do the following:
Here is the latest build: dxwrapper.zip |
dxwrapper-arx.log |
@Speedwagen, that is an old build. I never updated this thread with the latest build. However, I put a lot of fixes in since then. The released build should work for you. Make sure you disable both the in-game options: Bump Mapping and Rendering Fix. You also need to enable Note: I am using the GOG version of the game. Not sure if other versions work the same as the GOG version. Also, make sure you disable all compatibility settings: |
I think I got it to boot. Switched to software mode and the display looks like this haha. |
I got most of this game to run in Direct3D mode. There are still some lighting issues, but it seems to work other than that. Here is the updated build: dxwrapper.zip |
I fixed the color key issues. This build has almost all the issues fixed: dxwrapper.zip |
I just tried to run the DirectX 7 Wrapper provided by Kim.
Here is the log for Arx Fatalis.
dxwrapper-arx.log
The game does not boot.
The text was updated successfully, but these errors were encountered: