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 02 Dec 2024, 21:36

All times are UTC [ DST ]




Post new topic Reply to topic  [ 869 posts ]  Go to page Previous  1 ... 51, 52, 53, 54, 55, 56, 57 ... 87  Next
Author Message
PostPosted: 19 Jan 2016, 18:54 
Offline

Joined: 11 Dec 2014, 09:09
Posts: 2
Hi NightBits,

The patcher crashed on me when I run it. Is there any specific steps to apply the patcher?

Attachment:
File comment: MGSV Patcher crashed
MGSV Patcher Crash.jpg
MGSV Patcher Crash.jpg [ 72.64 KiB | Viewed 33031 times ]


[Update] Just checked your previous post. Seems like 5760x1080 resolution is not in the list of supported resolutions, so I guess that's why -_-


Top
 Profile  
 


PostPosted: 19 Jan 2016, 20:19 
Offline
Insiders
Insiders

Joined: 08 Sep 2005, 23:22
Posts: 223
NOOOOOOOOOOOOOO!!!!

The 1.071 updates seems to have broken jackfuste's Marker Fixer.

Whenever I try to activate the fix, MGSV crashes.

Can anyone else confirm?

This is killing me!! :(

_________________
Gigabyte GTX 980 - SLI

i7-4770k @4ghz

16GB Ram

Planar SA2311W 3D Vision monitors (x3)

Windows 7 x64 Ultimate SP1


Top
 Profile  
 
PostPosted: 19 Jan 2016, 21:54 
Offline
Insiders
Insiders
User avatar

Joined: 19 Dec 2011, 16:03
Posts: 521
Update for v. 1.0.7.1

For 4:3 (800x600, 1024x768 etc.)
mgsvtpp.7z

For 5:4 (1280x1024)
mgsvtpp.7z

For 2560x1080
mgsvtpp.7z

For 3440x1440
mgsvtpp.7z

For 48:10 (5040x1050; 5760x1200 etc.)
mgsvtpp.7z

For 48:9 (4800x900; 5760x1080 etc.)
mgsvtpp.7z


Markers fix:

For 2560x1080; 3440x1440
21_9_marker_fix_1_071.7z

For triple 16:9 screen 11520x2160; 5760x1080; 4800x900 etc.
48_9_marker_fix_1_071.7z

For triple 16:10 screen 5760x1200; 5040x1050 etc.
48_10_marker_fix_1_071.7z


Cheat Engine table:


mgsvtpp_1071.7z

First value should be changed
from
F3 0F 59 0D 83 8A FB FE
to
F3 0F 59 0D 87 8A FB FE
this fixes marker position.

Second value - 64, is size for marker and some ui elements.
Proper value should be calculated by formula:
64 * ((width/height)/1.77777)
For example, 64 * ((6000/1080)/1.77777) = 200.00087
So, 64 should be changed to 200.00087

Third value should be changed
from
F3 0F 5E A9 0C 01 00 00
to
F3 0F 59 A9 0C 01 00 00
this fixes sonar effect.

Fourth value should be changed
from
F3 0F 5E AA 0C 01 00 00
to
F3 0F 59 AA 0C 01 00 00
this fixes wind effect in the desert.

FOV Tool:

MGSTPP_FOV_1_071.7z


Top
 Profile  
 
PostPosted: 19 Jan 2016, 23:34 
Offline
Insiders
Insiders

Joined: 08 Sep 2005, 23:22
Posts: 223
jackfuste wrote:
Update for v. 1.0.7.1

For 4:3 (800x600, 1024x768 etc.)
mgsvtpp.7z

For 5:4 (1280x1024)
mgsvtpp.7z

For 2560x1080
mgsvtpp.7z

For 3440x1440
mgsvtpp.7z

For 48:10 (5040x1050; 5760x1200 etc.)
mgsvtpp.7z

For 48:9 (4800x900; 5760x1080 etc.)
mgsvtpp.7z


Markers fix:

For 2560x1080; 3440x1440
21_9_marker_fix_1_071.7z

For triple 16:9 screen 11520x2160; 5760x1080; 4800x900 etc.
48_9_marker_fix_1_071.7z

For triple 16:10 screen 5760x1200; 5040x1050 etc.
48_10_marker_fix_1_071.7z


Cheat Engine table:


mgsvtpp_1071.7z

First value should be changed
from
F3 0F 59 0D 83 8A FB FE
to
F3 0F 59 0D 87 8A FB FE
this fixes marker position.

Second value - 64, is size for marker and some ui elements.
Proper value should be calculated by formula:
64 * ((width/height)/1.77777)
For example, 64 * ((6000/1080)/1.77777) = 200.00087
So, 64 should be changed to 200.00087

Third value should be changed
from
F3 0F 5E A9 0C 01 00 00
to
F3 0F 59 A9 0C 01 00 00
this fixes sonar effect.

Fourth value should be changed
from
F3 0F 5E AA 0C 01 00 00
to
F3 0F 59 AA 0C 01 00 00
this fixes wind effect in the desert.

FOV Tool:

MGSTPP_FOV_1_071.7z


You, sir, are a life saver!! Or... an FOB saver at the least. :clap: :clap: :clap: :clap:

THANKS!!

_________________
Gigabyte GTX 980 - SLI

i7-4770k @4ghz

16GB Ram

Planar SA2311W 3D Vision monitors (x3)

Windows 7 x64 Ultimate SP1


Top
 Profile  
 
PostPosted: 20 Jan 2016, 01:49 
Offline
User avatar

Joined: 08 Sep 2015, 00:47
Posts: 37
Thank you jackfuste !!!


Top
 Profile  
 
PostPosted: 20 Jan 2016, 02:40 
Offline
User avatar

Joined: 13 Jan 2013, 00:01
Posts: 9
I don't understand why I can't use the IEEE-754 converter

I write 8040/1440 = 5,583333333333333 in the Value to Analyse and it just keep calculating without giving a result.

_________________
i7 4930k @ 4.5 Ghz with Quad R9 290x (Everything watercooled)
Triple 1440p monitors (middle is 4k but is ran in 1440p)


Top
 Profile  
 
PostPosted: 20 Jan 2016, 04:17 
Offline
User avatar

Joined: 03 Jan 2014, 02:59
Posts: 6
Where do I get v1.0.7.1 I know MGSV updated , but my .exe still says 1.0.7.0??


Top
 Profile  
 
PostPosted: 20 Jan 2016, 08:52 
Offline
Insiders
Insiders
User avatar

Joined: 19 Dec 2011, 16:03
Posts: 521
KaRLiToS wrote:
I don't understand why I can't use the IEEE-754 converter

I write 8040/1440 = 5,583333333333333 in the Value to Analyse and it just keep calculating without giving a result.

Try old version - http://babbage.cs.qc.cuny.edu/IEEE-754.old/Decimal.html
Input 5.583333333333333, but not 5,583333333333333

Grave-tm- wrote:
Where do I get v1.0.7.1 I know MGSV updated , but my .exe still says 1.0.7.0??

At last update, exe version still 1.0.7.0, but in game menu it shows Ver. 1.071
Image


Top
 Profile  
 
PostPosted: 20 Jan 2016, 09:52 
Offline

Joined: 19 Aug 2010, 23:05
Posts: 145
Again thanks to you Jackfuste.

Using your Cheat Table i can fix the markers but not flawlessly.
The x axis was correctly fixed but not the y that was "floating". And moreover the UI elements was some kind of "flatened".

So i search into your fix and found out that the X et Y ratio you force were not the good ones to apply to my specific resolution.
I mean the 16 & 9 ratios modified by yout cheat table.

In fact mine cannot be the 50 (X) and 9 (Y) used by the CT.
My specific resolution is 6012 * 1076 (for some reason the AMD bezel is a little bit broken which explain the 1076 instead of 1080).

The correct ratios for me would be 50.1 (X) and 8.96666 (Y) which is given by the next formula :
New X ratio = (Bezel width * basic 3 FHD screen X ratio) / basic 3 FHD screen width
Which gives 50.1 = (6012 * 48) / 5760
New Y ratio = (Bezel height * basic 1 FHD screen Y ratio) / basic 1 FHD screen height
Which gives 8.96666 = (1076 * 9) / 1080

Modyfing theses values at address accessed by the mulls assembly code could fix it the right way for me.

Attachment:
Capture.PNG
Capture.PNG [ 79.28 KiB | Viewed 5904 times ]


I could make a new cheat table but i put the exact 1420923F0 and 1420923F8 address as i don't know how to make it viable for everyone situation.
However, it seems to work for me every time i play the game.

I hope i make myself clear as i'm not english native. :D
Again big thank Jackfuste as you inspired me. :onethumb:


Top
 Profile  
 
PostPosted: 20 Jan 2016, 09:56 
Offline

Joined: 03 Jun 2015, 22:54
Posts: 5
I cant get it to work for MGO.
Anyone know how to?


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 869 posts ]  Go to page Previous  1 ... 51, 52, 53, 54, 55, 56, 57 ... 87  Next

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 2 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