Widescreen Gaming Forum

[-noun] Web community dedicated to ensuring PC games run properly on your tablet, netbook, personal computer, HDTV and multi-monitor gaming rig.
It is currently 24 Jun 2024, 14:25

All times are UTC [ DST ]




Post new topic Reply to topic  [ 767 posts ]  Go to page Previous  1 ... 55, 56, 57, 58, 59, 60, 61 ... 77  Next
Author Message
PostPosted: 23 Dec 2015, 05:00 
Offline
User avatar

Joined: 27 Nov 2015, 03:49
Posts: 23
Aiken Drum wrote:
It's just named that because you can circumvent the unnecessary launcher by swapping their names around. And no, doing it the right way around doesn't make any difference. :)


^ Slightly inaccurate. Same results, almost the same numbers. The base address goes to 0x3FCC0000 when I run the standard way, with files right way around and steam running the launcher. Otherwise everything pans out identically.


Top
 Profile  
 


PostPosted: 23 Dec 2015, 05:11 
Offline
User avatar

Joined: 27 Nov 2015, 03:49
Posts: 23
Waitaminute.

Aiken Drum wrote:
Image


Quote:
c_HackTool -> JMP candidate for ObjectAspectFix_cc, NOPS=1, Address=0x1401a6298


Where's the leading '1' I would have expected on the base address shown in the screenshot? Is this physical vs. virtual, or did the upper 32 bits get chopped off?


Top
 Profile  
 
PostPosted: 23 Dec 2015, 05:20 
Offline
Insiders
Insiders
User avatar

Joined: 14 Feb 2010, 13:39
Posts: 761
Well running it locally you can clearly see the problem.

Code:
DisplayDetection -> Scanning process for signs of SoftTH injection
c_HackTool -> Successfully opened process, ID=8272
Suspending Thread
HUDSafeZoneWide - Addr=Fallout4.exe+45B0770
HUDSafeZoneWide->X - Addr=Fallout4.exe+45B0770 (float=64.00)
HUDSafeZoneWide->Y - Addr=Fallout4.exe+45B0788 (float=36.00)
HUDSafeZone - Addr=Fallout4.exe+45B07A0
HUDSafeZone->X - Addr=Fallout4.exe+45B07A0 (float=20.00)
HUDSafeZone->Y - Addr=Fallout4.exe+45B07B8 (float=36.00)
HUDSafeZoneWide16x10 - Addr=Fallout4.exe+45B0740
HUDSafeZoneWide16x10->X - Addr=Fallout4.exe+45B0740 (float=15.00)
HUDSafeZoneWide16x10->Y - Addr=Fallout4.exe+45B0758 (float=15.00)
VATSZoomFix - Addr=Fallout4.exe+A8D47F
HUDFix - Addr=Fallout4.exe+2565F72
HUDFix_Cursor - Addr=Fallout4.exe+16843F8
HUDFix_Scoped - Addr=Fallout4.exe+E514A1
MouseFix_Regs - Addr=Fallout4.exe+255D8F0
MouseFix - Addr=Fallout4.exe+256B485
ObjectAspectFix - Addr=Fallout4.exe+DA6298
CenterMouse - Addr=Fallout4.exe+1019D49
CenterMouse1 - Addr=Fallout4.exe+1019D5F
CenterMouse2 - Addr=Fallout4.exe+1019D67
CenterMouse3 - Addr=Fallout4.exe+1019D84
CenterMouse4 - Addr=Fallout4.exe+1019D8C
FPFOV - Addr=Fallout4.exe+4598A30 (float=80.00)
TPFOV - Addr=Fallout4.exe+4598A18 (float=70.00)
WEPFOV - Addr=Fallout4.exe+1660F10
Un-Suspending Thread
Configure Success = true
Inject delay: 250ms, Configure() took: 1027ms, Adjusted Inject delay: -777ms
Actual delay: 3ms
Suspending Thread
X: 96.42
c_HackTool -> JMP candidate for ObjectAspectFix_cc, NOPS=1, Address=0x7ff7ea2a6298
c_HackTool -> JMP candidate for MouseFix_Regs_cc, NOPS=1, Address=0x7ff7eba5d8f0
c_HackTool -> JMP candidate for MouseFix_cc, NOPS=0, Address=0x7ff7eba6b485
c_HackTool -> JMP candidate for HUDFix_cc, NOPS=2, Address=0x7ff7eba65f72
c_HackTool -> JMP candidate for WEPFOV_cc, NOPS=2, Address=0x7ff7eab60f10
c_HackTool -> Successfully allocated 4096 bytes at 0x7ff7f1380000 for ASM block "Fixes"
c_HackTool -> Assembly compile was successful
Un-Suspending Thread


Pay attention to the bottom - your OS is behaving like it's 32bit, printf is atleast.

Can you screenshot the status tab after freshly starting it... it will report near the top how it see's your system. (although not in a detailed way, it should say 64bit compatible)

Image

Ignore the errors mine shows - using RDP, but note where it says Operating system is XYZ, 64Bit compatible.

_________________
Resident Jester - Flawless Widescreen - Widescreen gaming the way it should be.
[Steam Profile]

Want to keep Flawless Widescreen alive? Donate Here


Top
 Profile  
 
PostPosted: 23 Dec 2015, 05:40 
Offline
User avatar

Joined: 27 Nov 2015, 03:49
Posts: 23
HaYDeN wrote:
Well running it locally you can clearly see the problem.
...
Pay attention to the bottom - your OS is behaving like it's 32bit, printf is atleast.


Not actually seeing what you're seeing. Mine prints 64-bit values just fine, it's just that there are only nine hex digits in the values, vs your dozen or so. At a glance it looks like the debug log only shows 32 bits, but that's not the case.

That is interesting, though. Why are my actual addresses so different, hmm.

Quote:
Can you screenshot the status tab after freshly starting it... it will report near the top how it see's your system. (although not in a detailed way, it should say 64bit compatible)


Sure. It does say 64-bit compatible:

http://i.imgur.com/ut31KL8.png
Image

Actual OS is win7 ultimate x64, btw.


Top
 Profile  
 
PostPosted: 23 Dec 2015, 05:46 
Offline
Insiders
Insiders
User avatar

Joined: 14 Feb 2010, 13:39
Posts: 761
This is what you pasted in a earlier message:

Code:
c_HackTool -> JMP candidate for ObjectAspectFix_cc, NOPS=1, Address=0x1401a6298
c_HackTool -> JMP candidate for MouseFix_Regs_cc, NOPS=1, Address=0x14195d8f0
c_HackTool -> JMP candidate for MouseFix_cc, NOPS=0, Address=0x14196b485
c_HackTool -> JMP candidate for HUDFix_cc, NOPS=2, Address=0x141965f72
c_HackTool -> JMP candidate for WEPFOV_cc, NOPS=2, Address=0x140a60f10
c_HackTool -> Successfully allocated 4096 bytes at 0x1c7280000 for ASM block "Fixes"
c_HackTool -> Failed to compile assembly... Error during compile, check your assembly is accurate and valid.
c_HackTool -> Error occured near: jmp 0x14072629e (Relative Jump Out Of Range)


Here is what happens on my machine: (Windows 10 x64)

Code:
c_HackTool -> JMP candidate for ObjectAspectFix_cc, NOPS=1, Address=0x7ff7ea2a6298
c_HackTool -> JMP candidate for MouseFix_Regs_cc, NOPS=1, Address=0x7ff7eba5d8f0
c_HackTool -> JMP candidate for MouseFix_cc, NOPS=0, Address=0x7ff7eba6b485
c_HackTool -> JMP candidate for HUDFix_cc, NOPS=2, Address=0x7ff7eba65f72
c_HackTool -> JMP candidate for WEPFOV_cc, NOPS=2, Address=0x7ff7eab60f10
c_HackTool -> Successfully allocated 4096 bytes at 0x7ff7f1380000 for ASM block "Fixes"
c_HackTool -> Assembly compile was successful


ie. this demonstrates Printf is not behaving properly, I'm sure there are other functions misbehaving - I have tested 64bit functionality extensively on Windows 10 and Windows 8 but Windows 7 not so much.

64bit compatibility in general is a nightmere from experience, no matter how well you try and stick to "ideals" in terms of data types and practices.

[edit]
The problem will be printf, if you look in the Lua file, the addressing is all dynamic, I'm replacing strings and variables with addresses before I present the assembly to the Fasm DLL, so if it's broken in the debug window it will be broken when it generates the ASM to go out to FASM, where it consequently get's the binary back to inject.

Printf nomenclature for printing 64bit variables is a known rat's nest on windows, and linux too for that matter. #IFDEF nest ftw.

I lie, I'm actually using StringCchPrintf because of this exact issue when I first built it, behaviour wasen't consistent, I used that function hesitently because at the moment, FWS is Win32 only.

i.e. The problem lies here:
Code:
            if (Arch == 32) { tFormat = L"0x%x"; } else { tFormat = L"0x%llx"; }
            ....
            StringCchPrintf(buf,256,tFormat,Address);



[/edit]

_________________
Resident Jester - Flawless Widescreen - Widescreen gaming the way it should be.
[Steam Profile]

Want to keep Flawless Widescreen alive? Donate Here


Last edited by HaYDeN on 23 Dec 2015, 06:04, edited 1 time in total.

Top
 Profile  
 
PostPosted: 23 Dec 2015, 06:03 
Offline
User avatar

Joined: 27 Nov 2015, 03:49
Posts: 23
I'm still not seeing how printf is broken. My and your printfs both show 64-bit numbers. I've aligned the numbers and separated words for clarity:

Code:
c_HackTool -> JMP candidate for ObjectAspectFix_cc, NOPS=1, Address=0x    1 401a 6298
vs
c_HackTool -> JMP candidate for ObjectAspectFix_cc, NOPS=1, Address=0x 7ff7 ea2a 6298


Both are printing values > 0xffffffff successfully.

Edit: Granted, there's still the issue of the UI showing a 32-bit value, but at least during the log, they're still intact.


Last edited by Aiken Drum on 23 Dec 2015, 06:08, edited 1 time in total.

Top
 Profile  
 
PostPosted: 23 Dec 2015, 06:06 
Offline
User avatar

Joined: 27 Nov 2015, 03:49
Posts: 23
Maybe this is a dumb question, but am I receiving a 64-bit executable from Steam due to being on a 64-bit OS, but a person on win32 would receive a different executable that would be inherently more compatible with FWS?


Top
 Profile  
 
PostPosted: 23 Dec 2015, 06:18 
Offline
Insiders
Insiders
User avatar

Joined: 14 Feb 2010, 13:39
Posts: 761
Aiken Drum wrote:
I'm still not seeing how printf is broken. My and your printfs both show 64-bit numbers. I've aligned the numbers and separated words for clarity:

Both are printing values > 0xffffffff successfully.


The problem is - are they valid? I do not expect 64bit processes to be in the lower range, unless Windows 7's memory management significantly differs from the others.... keep in mind 64bit is heavily reliant on relative addressing and only really has a 48bit address space...

Perhaps I'm wrong, but you need to confirm the actual memory region that the executable is living in.

_________________
Resident Jester - Flawless Widescreen - Widescreen gaming the way it should be.
[Steam Profile]

Want to keep Flawless Widescreen alive? Donate Here


Top
 Profile  
 
PostPosted: 23 Dec 2015, 06:29 
Offline
User avatar

Joined: 27 Nov 2015, 03:49
Posts: 23
HaYDeN wrote:
keep in mind 64bit is heavily reliant on relative addressing... perhaps I'm wrong, but you need to confirm the actual memory region that the executable is living in.


Fair enough. Luckily, I can do that. I attached visual studio to the process and here's the useful bit of the modules window:

Code:
module                    address                            order
xinput1_3.dll             0000000000100000-000000000011E000* 17
RTSSHooks64.dll           00000000006E0000-000000000074C000* 82
steamclient64.dll         0000000054BC0000-00000000557FB000  55
tier0_s64.dll             0000000058E00000-0000000058FE4000  59
msvcr90.dll               000000005DA20000-000000005DAC3000  83
vstdlib_s64.dll           0000000069C50000-0000000069CB4000  60
sfc.dll                   000000006D6B0000-000000006D6B3000  47
steam_api64.dll           000000006D780000-000000006D7B7000  31
X3DAudio1_7.dll           0000000071EC0000-0000000071EC9000  16
user32.dll                0000000076C60000-0000000076D5A000   5
kernel32.dll              0000000076D60000-0000000076E80000   3
ntdll.dll                 0000000076E80000-0000000077029000   2
psapi.dll                 0000000077050000-0000000077057000  54
Fallout4Launcher.exe      000000013F420000-000000014728D000   1
nvwgf2umx.dll             000007FEDF870000-000007FEE0A1A000  70
dsound.dll                000007FEE57B0000-000007FEE5838000  80
BtMmHook.dll              000007FEE6240000-000007FEE627F000  67
dxgidebug.dll             000007FEECB90000-000007FEECBB6000  68
d3d11.dll                 000007FEECBC0000-000007FEECD95000  35
dxgi.dll                  000007FEECDA0000-000007FEECDFD000  36
sfc_os.dll                000007FEF1200000-000007FEF1210000  48
XAudio2_7.dll             000007FEF32B0000-000007FEF333B000  78
GameOverlayRenderer64.dll 000007FEF3340000-000007FEF34DC000  53
AcGenral.dll              000007FEF34E0000-000007FEF3531000  45
AcXtrnal.dll              000007FEF3540000-000007FEF39A7000  44
mpr.dll                   000007FEF72B0000-000007FEF72C8000  43
AcLayers.dll              000007FEF7340000-000007FEF739A000  41
msvcr110.dll              000007FEF73A0000-000007FEF7474000  33
msvcp110.dll              000007FEF7480000-000007FEF7527000  32
bink2w64.dll              000007FEF7850000-000007FEF78DB000  25
GFSDK_GodraysLib.x64.dll  000007FEF7910000-000007FEF796A000  39
comctl32.dll              000007FEF83D0000-000007FEF8470000  66
nvapi64.dll               000007FEF8470000-000007FEF87BC000  72
libScePad.dll             000007FEF8E40000-000007FEF8E6B000  22
winnsi.dll                000007FEF9340000-000007FEF934B000  30
IPHLPAPI.DLL              000007FEF9350000-000007FEF9377000  28
AudioSes.dll              000007FEF9780000-000007FEF97CF000  77
winmm.dll                 000007FEF9810000-000007FEF984B000  23
winspool.drv              000007FEF98B0000-000007FEF9921000  42
sizerhook64.dll           000007FEF9B20000-000007FEF9B29000  65
winhttp.dll               000007FEFAFB0000-000007FEFB021000  26
dwmapi.dll                000007FEFB090000-000007FEFB0A8000  38
webio.dll                 000007FEFB100000-000007FEFB164000  27
avrt.dll                  000007FEFB2A0000-000007FEFB2A9000  79
hid.dll                   000007FEFB2B0000-000007FEFB2BB000  24
propsys.dll               000007FEFB2F0000-000007FEFB41C000  76
MMDevAPI.dll              000007FEFB420000-000007FEFB46B000  75
powrprof.dll              000007FEFB470000-000007FEFB49C000  81
version.dll               000007FEFB800000-000007FEFB80C000  37
bcryptprimitives.dll      000007FEFC0A0000-000007FEFC0EC000  73
rsaenh.dll                000007FEFC160000-000007FEFC1A7000  63
cryptsp.dll               000007FEFC460000-000007FEFC478000  62
bcrypt.dll                000007FEFC5B0000-000007FEFC5D2000  71
secur32.dll               000007FEFC860000-000007FEFC86B000  61
sspicli.dll               000007FEFCA30000-000007FEFCA55000  46
apphelp.dll               000007FEFCA60000-000007FEFCAB7000  40
cryptbase.dll             000007FEFCAC0000-000007FEFCACF000  64
msasn1.dll                000007FEFCC20000-000007FEFCC2F000  57
profapi.dll               000007FEFCC30000-000007FEFCC3F000  50
userenv.dll               000007FEFCC50000-000007FEFCC6E000  49
devobj.dll                000007FEFCD10000-000007FEFCD2A000  21
cfgmgr32.dll              000007FEFCD60000-000007FEFCD96000  19
KernelBase.dll            000007FEFCDA0000-000007FEFCE0C000   4
crypt32.dll               000007FEFCE30000-000007FEFCF9D000  56
wintrust.dll              000007FEFCFA0000-000007FEFCFDB000  69
sechost.dll               000007FEFCFE0000-000007FEFCFFF000  11
rpcrt4.dll                000007FEFD000000-000007FEFD12D000  12
gdi32.dll                 000007FEFD590000-000007FEFD5F7000   6
clbcatq.dll               000007FEFD600000-000007FEFD699000  74
oleaut32.dll              000007FEFD6A0000-000007FEFD777000  20
msctf.dll                 000007FEFD780000-000007FEFD889000  52
shell32.dll               000007FEFD890000-000007FEFE619000  13
msvcrt.dll                000007FEFE620000-000007FEFE6BF000   9
imagehlp.dll              000007FEFE720000-000007FEFE739000  58
setupapi.dll              000007FEFE740000-000007FEFE917000  18
imm32.dll                 000007FEFE920000-000007FEFE94E000  51
ws2_32.dll                000007FEFE950000-000007FEFE99D000  34
ole32.dll                 000007FEFEC90000-000007FEFEE93000  15
lpk.dll                   000007FEFEEA0000-000007FEFEEAE000   7
usp10.dll                 000007FEFEEB0000-000007FEFEF7A000   8
shlwapi.dll               000007FEFEF80000-000007FEFEFF1000  14
advapi32.dll              000007FEFF0A0000-000007FEFF17B000  10
nsi.dll                   000007FEFF180000-000007FEFF188000  29


I included load order in case you wanted that info.


Last edited by Aiken Drum on 23 Dec 2015, 07:12, edited 2 times in total.

Top
 Profile  
 
PostPosted: 23 Dec 2015, 06:44 
Offline
Insiders
Insiders
User avatar

Joined: 14 Feb 2010, 13:39
Posts: 761
OK it is using a range much lower than where the rest of the OS is living - which different from later versions of Windows.

I'll have to look into it, looks like a bug on my side - altho I really have to ask, haha, why the hell are you still running Windows 7.

_________________
Resident Jester - Flawless Widescreen - Widescreen gaming the way it should be.
[Steam Profile]

Want to keep Flawless Widescreen alive? Donate Here


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 767 posts ]  Go to page Previous  1 ... 55, 56, 57, 58, 59, 60, 61 ... 77  Next

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 11 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  




Powered by phpBB® Forum Software © phpBB Group