Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/ProjectSetup.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,4 +80,8 @@ If you have built your mod in `Debug` configuration and a supported IDE/Debugger

![Debugger Launch](./Images/DebuggerLaunch.png)

Select your IDE/Debugger of choice and have fun.
Select your IDE/Debugger of choice and have fun.

!!! warning

Some games running [Steam's DRM](https://partner.steamgames.com/doc/features/drm) may not trigger breakpoints after a debugger is attached. To get around this, unpack the executable first (with utilities such as [Steamless](https://github.com/atom0s/Steamless)) and edit the application within Reloaded-II to use the new executable.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct.

Has been an annoyance of mine for a while too- I even have a special code path in the loader (as you may have noticed) for handling this DRM, since game is encrypted at boot.

(It mass hooks Windows functions then loads when one is called)

In any case, I would suggest replacing original executable for simplicity instead, instructions wise.

I once considered bundling Steamless but the license (at the time) has not allowed it. That has however since changed IIRC.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also thinking about it.

The games which use this DRM have a console message attached to them when the .bind section is enabled. So you can tell in the Reloaded logs.

So maybe make a subsection, and mention this in a troubleshooting section. A copy of the console message may be helpful to attach.

Loading