You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This line and a few others in that file treat the "precision bloom" TU1 value as if it's serialized as a float between 0 and 10. Disassembling MCC's haloreach.dll, I see it's actually serialized as a float between 0 and 2 (same as most TU1 settings). This means that current and past versions of MegHalomaniac need to be provided a multiplier of 5 to serialize 100% bloom, to compensate for the incorrect range.
Only the TU1 Magnum modifiers are on a scale of 0 to 10.
If I have my x64dbg expression syntax right, then for haloreach.dll version 1.2862.0.0 (the build available as of this writing), the relevant code for loading the setting will be at offset 0xCE1AC from the module base.
The text was updated successfully, but these errors were encountered:
This line and a few others in that file treat the "precision bloom" TU1 value as if it's serialized as a float between 0 and 10. Disassembling MCC's haloreach.dll, I see it's actually serialized as a float between 0 and 2 (same as most TU1 settings). This means that current and past versions of MegHalomaniac need to be provided a multiplier of 5 to serialize 100% bloom, to compensate for the incorrect range.
Only the TU1 Magnum modifiers are on a scale of 0 to 10.
If I have my x64dbg expression syntax right, then for haloreach.dll version 1.2862.0.0 (the build available as of this writing), the relevant code for loading the setting will be at offset 0xCE1AC from the module base.
The text was updated successfully, but these errors were encountered: