Numpad 1: Infinite Camera Energy
Numpad 2: Unlimited Batteries
Change hotkeys directly on the trainer/editor by selecting your desired hotkey via a drop down menu.
To save hotkeys press right mouse button on a hotkey and press save button on context menu.
A file will be created inside of the trainer/editor directory. If this file is missing or damaged the standard hotkey setup will
To set up hotkeys for the editor, click on the small arrow on the right side of the apply button. A dropdown menu opens where you
need to click on 'Set Hotkey'.
Now press any key you wish and the hotkey is set. To CANCEL press ESC (Escape). Also mouse buttons (left, right & middle) are
disabled for hotkeys.
Open 'Controller HowTo' tab at the trainer interface for a detailed instruction on how to use a controller. Don't forget to
activate 'Use Xbox 360 controller' at the main page.
System.Exception: 'System.Exception' Throw
Location: Outlast_64bit_CH.MemoryEditor.Memory.RemoveProtection(String ProcessName, Int64 AddressOfStart, Int32 SizeToRemoveProtectionInBytes)
Location: Outlast_64bit_CH.Form1.tHotkeys_Tick(Object sender, EventArgs e)
Location: System.Windows.Forms.Timer.OnTick(EventArgs e)
Location: System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
It's been patched five times so far.
(Various smaller issues like the 32-bit exe not working or some users getting a black screen - also with the 32-bit exe - plus some other stuff.)
Maybe I should make a game. Hmm...
(Which is odd in it's own way since that's a pretty important Windows program for running any D3D game from 2006 or so and later.)
I can't find any details on what the four exe updates did other than some posts on the forums by the developers and a few users stating how the 32-bit black-screen issue had been fixed or how the game started without having to use the 64-bit exe file but I assume these four updates were pretty much rushed and thus only fix one or two things instead of planning a single larger update for later this week or something.
(Or testing the game better before releasing the build on Steam, that could work, heh.)
Anyways just a small heads-up that the developers seem pretty active with updating the game and due to the various updates it might be possible that the trainer is not yet fully compatible with the latest version, thus the above error message.
(It's probably fairly easy to fix and upload a updated trainer for the current version but who knows when the game will update next.)
Oh and speaking of updates Creative Ensemble is planning weekly Friday patches for Rome 2 for the foreseeable future but if it's just once a week it shouldn't be too problematic for trainer compatibility.
(Although it's right at the weekend unfortunately.)
EDIT: Steam does make updates fairly convenient for the developers though from my understanding of it, also there was a Greenlight update recently where a massive 100 games were accepted so I guess we'll see more situations like these although it's not like it's just a indie game thing. (Or smaller studios.)
[Edited by LordJB, 9/5/2013 8:57:51 AM]
SO Win7 x64
[Edited by halnegro, 9/5/2013 9:01:36 AM]
That should confirm if it is the updated exe file that's causing the problem.
firewall and other security software.
on trainer and game.
version and distribution.