Skip to content
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

OCAT crashes HITMAN #40

Open
brunogm0 opened this issue Sep 19, 2018 · 8 comments
Open

OCAT crashes HITMAN #40

brunogm0 opened this issue Sep 19, 2018 · 8 comments
Assignees

Comments

@brunogm0
Copy link

brunogm0 commented Sep 19, 2018

HITMAN v 1.14.2.0

win10 pro

Crash when enabling Overlay.

@aurolou
Copy link
Collaborator

aurolou commented Sep 20, 2018

I pushed a fix, you can get the build here.

I noticed, that OCAT also hooks into the launcher, which can cause issues. To prevent these, you can do one of the following:

start the launcher -> (set your options as you like) -> enable the overlay -> start the game via the launcher
or
add Launcher.exe to the blackList.txt.

Hope this helps and the new build fixes your issue :)

@brunogm0
Copy link
Author

brunogm0 commented Sep 20, 2018

With OCAT open but no overlay active; the crash happens with message breakpoint. After this other attempts crashes with the old message but other address.

@aurolou
Copy link
Collaborator

aurolou commented Sep 20, 2018

Unfortunately, I can't reproduce the crash locally, the fix in version 1.2.0.168 solved the issue for me. So I need some further information from you to figure out the root cause of the problem :)

Do I understand correctly, that you just start OCAT, and without even enabling the overlay, HITMAN crashes on launch, but when OCAT is not running, HITMAN does launch without problems?

And how do you enable the overlay? Do you click on 'Start Overlay' in the Capture tab, or do you use the Advanced tab by starting HITMAN via the OCAT-UI? If you use the 'Start Overlay' in the Capture tab option, when do you turn it on: before you start the Launcher, or after you start the launcher but before you start the actual Hitman game? Do you run Hitman using DX11 or DX12?

Thanks :)

@brunogm0
Copy link
Author

brunogm0 commented Sep 21, 2018

Do I understand correctly, that you just start OCAT, and without even enabling the overlay, HITMAN crashes on launch, but when OCAT is not running, HITMAN does launch without problems?

Yes, but with launcher.exe in blacklist it changes to only crash after few seconds in the game.
ocat_hitman

Silent crashes with DX11 instead of DX12 (error as in the picture);
OCAT click "Start Overlay on" silent crash launcher at options click;
OCAT open but overlay off, allows to change options in launcher.exe;

Usually "click on 'Start Overlay' " but also tested advanced tab. In this case the error dialog is immediate.
Also, tested advanced without "inject overlay at start", same instant crash dialog;
If using advanced but selecting Launcher.exe, the error dialog changes to "bad conversion";

If overlay off then game start, hitman.exe is allocating memory steadly; (then overlay on) -> crash dialog happens only at first image print; aka, hitman.exe still loads when "overlay on" after start.
I have the impression that after a few tries OCAT behaves differently maybe it stores something.
GameOverlayLog.txt
PresentMonLog.txt

Other tests:
Never show overlay in: hitman, skullgirls or FFXV;
Showed on Superposition, Quake Champions

ps.: RX460 18.8.1

@aurolou
Copy link
Collaborator

aurolou commented Sep 25, 2018

Thanks for the details! I could locally observe a thrown exception which I think is related to your issue, now I am looking for a way to solve it :)

@aurolou
Copy link
Collaborator

aurolou commented Nov 22, 2018

Hey, sorry for the delay. This version should work for FFXV, if you launch the game from OCAT (Launch App tab) and add as commandline argument: steam://run/637650

For Hitman, the global hook works for me, if not you can also try the explicit hook (launch the game directly from OCAT) with commandline argument: steam://run/236870

Make sure the steam client is running.

@rys
Copy link
Contributor

rys commented Dec 17, 2018

Did that version fix your issue, @brunogm0?

@brunogm0
Copy link
Author

Sorry, my SSD failed and so i could not test it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants