Running microsoft windows non-core edition
![running microsoft windows non-core edition running microsoft windows non-core edition](https://i.imgur.com/XGVvc9N.png)
![running microsoft windows non-core edition running microsoft windows non-core edition](https://i.ytimg.com/vi/tmqNLv02KIk/hqdefault.jpg)
List of normal hotkeys KeyĬommand: Selected Minifigure to drop Dynamite and start Tick DownĬommand: Selected Minifigure to get in Registered Vehicle TODO: Original AI bug Configurable hotkeys "Idle Syndrome" Unit stops performing tasks Change the flags operation on the same line to |= MainFlags::MAIN_FLAG_DUALMOUSE to set, rather than unset, the flag.Change the parsed command line option string to "-dualmouse".flags &= ~MainFlags::MAIN_FLAG_DUALMOUSE Īpply the following changes to the Figure B source line, so that OpenLRR correctly matches LRR behavior: If ( Util_StrIStr(lpCmdLine, "-nodualmouse ")) mainGlobs. Reference Figure A: Following LRR and disabling dual mouse before parsing the command line. While in Gods98 source, the setting is implemented as a negative option to disable the feature: -nodualmouseĬurrently, OpenLRR mistakenly uses the -nodualmouse command line option (as per Gods98 in Figure B) while also disabling the feature by default (as per LRR in Figure A), forcing the feature to always be off.In LRR, the dual mouse setting is implemented as a positive option to enable the feature: -dualmouse.dualmouse command line option has no effect Describe the issue Meaning this may not be related to commanding. It's possible that a selected unit is exempt from disappearing until given a command/or being unselected. TODO: Link "Rocky Raiders" video evidence with included Bats spazzing out.īats are observed to begin flying in sporadic and unpredictable patterns just before (or after?) all units disappear. Past recordings of this phenomenon have also shown that the issue seems to trigger right around the time of giving a unit an instruction (slightly before actually). This triggered right around the time frame that a minifigure was selected and being given an instruction to get into a vehicle. These seem to appear only after that unit calls Routing_BuildPoints after a patient zero unit had created the initial "NaN Routing state". Other units (3) were soon after logged with NaN (IND) values in their routing data. These values then permeated through the unit's entire routing data, immediately after as Routing_BuildPoints was called. Original bug, affects all Minifigure/RockMonster (Creature)-type units.Ī unit was logged trying to change the length of a (0, 0) vector which resulted in divide by zero xy values. "NaN Routing" Divide by 0 causes units to disappear VirtualAddress (+offset in address caused by.Size (+0x14 for added dll import openlrr.dll).OPTIONAL HEADER: SizeOfImage (+virtual size diff of.OPTIONAL HEADER: SizeOfInitializedData (+file size diff of.FILE HEADER: NumberOfSections (+1 for.This ensures our import will be placed in a fixed position that won't unexpectedly change. rsrc is so that anyone can freely modify executable resources without potentially breaking our hook into openlrr.dll::StartOpenLRR. Replace the main icon resource with "teal-OR" and include any other desired resources.
#Running microsoft windows non core edition update#
Update the Import and Resource directory RVAs to point to their new location.Overwrite LegoRR.exe::WinMain with a call to int _cdecl openlrr.dll::StartOpenLRR that pushes the same 4 parameters, then cleans up the stack and returns.Append a new import for openlrr.dll and include the function StartOpenLRR.Insert a new Import Directory PE section (.The goal is to import the OpenLRR codebase contained in openlrr.dll, and replace the original LegoRR.exe::WinMain entrypoint with a call to openlrr.dll::StartOpenLRR. OpenLRR must be built from the Masterpiece executable. The OpenLRR executable should be buildable without relying on LRR:CE, and should be created from a fresh Masterpiece executable. Enable use of VS debugger (which can't be done through Injector, due to it launching a new process).Ĭurrently, OpenLRR debugging has been performed by using a modified version of LegoRRCE.exe with changed imports.Ensure all users are running the same Masterpiece executable.And preferably hook the WinMain function with a call to initialise OpenLRR (which avoids all race conditions caused by DllMain).Import the openlrr.dll codebase to inject all modifications.Similar to other projects LegoRRCE.exe and OpenRCT2.exe, OpenLRR needs a proper distributable executable. OpenLRR's Issues Distributable OpenLRR executable Describe the issue