Widescreen Gaming Forum

HaYDeN wrote: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.

Two reasons:

1) I worked at MS while 8.0 was in development. Everyone had to use it. What I developed was a hatred for 8.0. 8.1 was better, but at that point I wasn't interested.

2) I'd upgrade to 10 right now if it weren't for nVidia's awful drivers of late. I run four-way SLI of the older GTX 680's, across three Surround monitors, and support for marginal users like me has become likewise marginal. I read their forums and win10 support for even very recent legacy cards is anything but stellar. I'm looking at switching to a single 980ti and maybe a single 21:9 monitor just to get rid of the headaches. I'm not sure it'll be a whooole lot better, but at least the SLI factor is out of the equation.

So, yeah, there's why. Otherwise I have no issues with switching to 10. I'd actually like to, since VS2015 prefers to run on 10 and I'd like to play with VS2015.

By the way, you're right that Win7, 8, and 10 use differing methods of allocating the process memory space. Usually it's an attempt to make the naughtier forms of code injection more difficult. I actually just tried diddling with the mitigation bits for this app. I could make it slightly random, but only in a small range near what we've been seeing. I couldn't get it noticeably higher than that. Specifically disabling the feature just gave me what I already had, since it's the OS default.

HaYDeN wrote: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.

Actually a lot of people still using windows 7 for many reasons. 1- most hate the metro interface, even though you can change it some what. 2- last stats showed that only 7% the computers in the world still running win 10. Might be lower now as that was about a month ago sats, they were steadily dropping 5% a month for a while.
P.S. wont get into any chat from anyone over any reasons of Win 10, what ever side me or others reside on.

Followed your steps and does not work for me in Fallout 4 tends to randomly crash when starting up game though.

Just wanted to report that in windows 10 x64 it's working well, stable after hours of play. My only issue is some graphics artifacting on the compass, and the crafting interface displaying small images. Just minor things considering the whole. My thanks.

@Daimond, Metro is gone in 10, not sure what you are talking about with that.

Aiken Drum wrote:By the way, you're right that Win7, 8, and 10 use differing methods of allocating the process memory space. Usually it's an attempt to make the naughtier forms of code injection more difficult. I actually just tried diddling with the mitigation bits for this app. I could make it slightly random, but only in a small range near what we've been seeing. I couldn't get it noticeably higher than that. Specifically disabling the feature just gave me what I already had, since it's the OS default.

I tested it in a VM, WIndows 7 x64 - worked fine... address behaviour was the same as you found...

Must be something specific to your system.

Haven't had a chance to play it extensively yet, been busy with xmas stuff, but I can report here too that the FWS fix seems to be working perfectly for me so far. Windows 10, 64bit, 5760x1080. Much appreciated! Haven't come across a menu yet that hasn't looked great.

Hey everyone! Just found this thought I would share. For those annoyed with the vignette, darkening of power armor....Check this mod out.

http://www.nexusmods.com/fallout4/mods/ ... w%3D&pUp=1

Will try today but wanted to give everyone a heads up! Been looking for this for a while to get a clean looking power armor interface.

Hey gang. Lost track of progress of flawless widescreen fallout 4 support. Looks like beta is out? I am a long time Hayden supporter but got busy with Xmas. Can a kind soul please point me to the newest version?

And is there a guide on undoing the changes we made while waiting?

man Ive had some time to search around today.

BTW - thanks for the amazing interfance.ba2 file. Makes the game playable! Will try the flawless fix ASAP when I get a chance.

Helifax, the other WSG guru - posted this on the nvidia forum. Might be worthfile for those of you with sli gaming rigs. Unfortunately I have crossfire

https://forums.geforce.com/default/topi ... d-others-/

I just installed Hayden's plugin and I seem to be having problems with the HUD as well =(.

I removed all the changes to the ini files and extra interface files I put in for previous fixes and used Steam to check all the files again then I edited the Faullout4Prefs.ini to change the resolution to 5760*1080 and ran the game with FFS running and the plugin installed. FFS' console says it detects the game and applies all the fixes, I can see things like the dark green boxes appearing where they are supposed to be showing up and and all that seems to work well but I don't see any text during the loading screens (just the image) and once in game the only HUD element I can see is the compass at the bottom. I can't see the HP or AP bar, can't see the ammo and not even the flashlight icon when it's turned on.

Here's a screenshot of what I can see in the game:
http://i.imgur.com/2LTPcCn.jpg

Here's an example of a loading screen:
http://i.imgur.com/eYTNZcc.jpg

And a couple screenshots of FFS:
http://i.imgur.com/jhiQndI.png
http://i.imgur.com/qEweFFm.png
http://i.imgur.com/MZlO1Hx.png


Any thoughts? Am I missing something?.

HaYDeN wrote:Here is the current state for Surround:
...
[edit]
Released

If you wish to try it, I would strongly recommend you return any modified UI flash files back to their defaults, and any INI edits relating to the HUD to default initially.

About 64 lines of new JIT assembly being injected by the patch, which is more than Skyrim required.
[/edit]

Hayden, appreciate your work on it. Hit one issue. Using it while playing with an Xbox controller, the map never gets a cursor. Can zoom in and out but without a cursor you cannot select locations for fast travel, and scrolling the map doesn't work much except for scrolling left.

Surround, 5760x1200, removed .ini changes and had Steam revalidate cache.

GregR wrote:

HaYDeN wrote:Here is the current state for Surround:
...
[edit]
Released

If you wish to try it, I would strongly recommend you return any modified UI flash files back to their defaults, and any INI edits relating to the HUD to default initially.

About 64 lines of new JIT assembly being injected by the patch, which is more than Skyrim required.
[/edit]

Hayden, appreciate your work on it. Hit one issue. Using it while playing with an Xbox controller, the map never gets a cursor. Can zoom in and out but without a cursor you cannot select locations for fast travel, and scrolling the map doesn't work much except for scrolling left.

Surround, 5760x1200, removed .ini changes and had Steam revalidate cache.

Right click the plugin in FWS and goto "Reinstall plugin" and report back.

Do not enable gamepad mode while using the keyboard or it will cause issues, they operate differently.

Who knows if the new change breaks anything else or if anything else is broken, it's not the kind of game I'd play with a gamepad.

Hayden,
Thanks for all your work! I am going to Create a PP account in a little and Thank you more substantially. I am having small leftover issues. The Text that displays on loading screens is missing as well as popup messages like when you exit out of Workshop and get the informative messages about how to return to workshop using the shortcut. It seems like something is trying to display as i get a ghost of the background sometimes. I also dont see my HP/AP like I should.
nVidia surround 16:9
Windows 10
no extra controllers
I am launching the game using the alpha of ModOrganizer but dont think its having any side effect from that. Your program/plugins have always played nice with ModOrganizer. I only mention it because it also touches the exe at runtime to inject the VFS and he is re-writing in 64 bit.

EDIT: Just to test and make sure that it wasn't an issue I did a pure Steam launch so that no plugins would load and no ModOrganizer. the mentioned items above were still missing. Any idea's? I will be happy to test solutions for you since I am the one asking.

Robert

rdunlap wrote:Hayden,
Thanks for all your work! I am going to Create a PP account in a little and Thank you more substantially. I am having small leftover issues. The Text that displays on loading screens is missing as well as popup messages like when you exit out of Workshop and get the informative messages about how to return to workshop using the shortcut. It seems like something is trying to display as i get a ghost of the background sometimes. I also dont see my HP/AP like I should.
nVidia surround 16:9
Windows 10
no extra controllers
I am launching the game using the alpha of ModOrganizer but dont think its having any side effect from that. Your program/plugins have always played nice with ModOrganizer. I only mention it because it also touches the exe at runtime to inject the VFS and he is re-writing in 64 bit.

EDIT: Just to test and make sure that it wasn't an issue I did a pure Steam launch so that no plugins would load and no ModOrganizer. the mentioned items above were still missing. Any idea's? I will be happy to test solutions for you since I am the one asking.

Robert

I've only ever seen that happen when the displays are detected incorrectly - what does FWS report as your detected resolution and break down of displays on main status page.

rdunlap wrote:Hayden,
Thanks for all your work! I am going to Create a PP account in a little and Thank you more substantially. I am having small leftover issues. The Text that displays on loading screens is missing as well as popup messages like when you exit out of Workshop and get the informative messages about how to return to workshop using the shortcut. It seems like something is trying to display as i get a ghost of the background sometimes. I also dont see my HP/AP like I should.
nVidia surround 16:9
Windows 10
no extra controllers
I am launching the game using the alpha of ModOrganizer but dont think its having any side effect from that. Your program/plugins have always played nice with ModOrganizer. I only mention it because it also touches the exe at runtime to inject the VFS and he is re-writing in 64 bit.

EDIT: Just to test and make sure that it wasn't an issue I did a pure Steam launch so that no plugins would load and no ModOrganizer. the mentioned items above were still missing. Any idea's? I will be happy to test solutions for you since I am the one asking.

Robert

Okay,
I am reduced to quoting myself. <sigh> I should learn to take my own advice. Guys Hayden TOLD us to get rid of the ini tweaks we were using with the ba2 fix and I thought I had. I was poking around trying to see if I had any left over and just decided to delete them and let the launcher re-create them. Now Hayden's fix is solid and nothing is out of place.

Hayden would it help you if I sent you the old Ini files *(i have them in a zip) so you can locate the setting(s) that are incompatible? its apparent that at least one settings change is incompatible.

EDIT2: Its the interface safe zone changes that are messing up the text pop in boxes. I added the ini tweaks one at a time to find the issue. The safezone changes absolutely kill the fix on the pop in boxes and the HP/Ammo display. So! If I had did it correct to start with then I would not have had that issue.

Robert

HaYDeN wrote:

rdunlap wrote:Hayden,
Thanks for all your work! I am going to Create a PP account in a little and Thank you more substantially. I am having small leftover issues. The Text that displays on loading screens is missing as well as popup messages like when you exit out of Workshop and get the informative messages about how to return to workshop using the shortcut. It seems like something is trying to display as i get a ghost of the background sometimes. I also dont see my HP/AP like I should.
nVidia surround 16:9
Windows 10
no extra controllers
I am launching the game using the alpha of ModOrganizer but dont think its having any side effect from that. Your program/plugins have always played nice with ModOrganizer. I only mention it because it also touches the exe at runtime to inject the VFS and he is re-writing in 64 bit.

EDIT: Just to test and make sure that it wasn't an issue I did a pure Steam launch so that no plugins would load and no ModOrganizer. the mentioned items above were still missing. Any idea's? I will be happy to test solutions for you since I am the one asking.

Robert

I've only ever seen that happen when the displays are detected incorrectly - what does FWS report as your detected resolution and break down of displays on main status page.

It is getting my displays and the layout information correct. See my other post for the real issue. NB: there are errors reporting on the status page about failure to write to process memory. 5 different errors. Can i grab a log file and send to you? or is this expected. on the skyrim fix I never see any error messages.

Robert

rdunlap wrote:It is getting my displays and the layout information correct. See my other post for the real issue. NB: there are errors reporting on the status page about failure to write to process memory. 5 different errors. Can i grab a log file and send to you? or is this expected. on the skyrim fix I never see any error messages.
Robert

It may report some errors at startup if it tries to start writing too quickly or your pc is loading it slowly, ie it's on a HDD instead of a SSD, it has to be aggressive because it needs to modify something that Fallout loads within 200ms of it starting, it may begin (attempting) to write to the process before it's fully loaded into memory.

Basically you can ignore it, generally...

rdunlap wrote:EDIT2: Its the interface safe zone changes that are messing up the text pop in boxes. I added the ini tweaks one at a time to find the issue. The safezone changes absolutely kill the fix on the pop in boxes and the HP/Ammo display. So! If I had did it correct to start with then I would not have had that issue.
Robert

Yes, the safezone values when the fix is applied are from the extremes of the new HUD width, (ie 1920 instead of 5760) which would effectively push them off screen.

There's still some stuff that's broken such as the markers not lining up, the compass markers in the power armor and the workshop icons.

HaYDeN wrote:

rdunlap wrote:It is getting my displays and the layout information correct. See my other post for the real issue. NB: there are errors reporting on the status page about failure to write to process memory. 5 different errors. Can i grab a log file and send to you? or is this expected. on the skyrim fix I never see any error messages.
Robert

It may report some errors at startup if it tries to start writing too quickly or your pc is loading it slowly, ie it's on a HDD instead of a SSD, it has to be aggressive because it needs to modify something that Fallout loads within 200ms of it starting, it may begin (attempting) to write to the process before it's fully loaded into memory.

Basically you can ignore it, generally...

rdunlap wrote:EDIT2: Its the interface safe zone changes that are messing up the text pop in boxes. I added the ini tweaks one at a time to find the issue. The safezone changes absolutely kill the fix on the pop in boxes and the HP/Ammo display. So! If I had did it correct to start with then I would not have had that issue.
Robert

Yes, the safezone values when the fix is applied are from the extremes of the new HUD width, (ie 1920 instead of 5760) which would effectively push them off screen.

There's still some stuff that's broken such as the markers not lining up, the compass markers in the power armor and the workshop icons.

as is usually the case if end user followed directions then it would not happen. That was precisely what was happening because the ghosts I was seeing were on the left and right monitors not the center where you place all the nice Interface fixes. GREAT WORK sir. as I said earlier I am going to Donate to keep you going on stuff like this. You have been behind the scenes providing us with a Flawless Widescreen experience for a long time.

Happy Holidays Everyone!

Robert

EDIT: I moved the Flawless folder to my SSD with the Steam Folders and the errors disapeared except for 1 but everything works great so I am NOT concerned. 64 bit stuff is as funky as a Friday night funhouse

I have not tried the nexus mod fix, the real question is my fix adding any real value? or do you lose more than you gain (ie markers)

HaYDeN wrote:I have not tried the nexus mod fix, the real question is my fix adding any real value? or do you lose more than you gain (ie markers)

I personally dont think I am losing out. What markers are supposed to be missing?? If you are talking about PA HUD stuff the PA is not useful when you are seeking good markers in widescreen. If I am hunting around via markers to find something I just leave the PA at the base and go armor up and hit the road. No fix I have tried made that any better. You are solid and do not add any overhead to the game like a mod does. The Nexus one was not stable enough for me. I would get random parts not showing or just showing wrong. I figured it was just the game engine not playing nice. That is what makes your approach preferable really. In Skyrim or Fallout. You get in place with new values without the engine knowing or caring about it. Other approaches leave the engine open to mess with them when it is feeling grumpy. *(often grumpy) You are the ONLY widescreen fix that puts my console on the main display only. All other fixes I have tested *(being a widescreen gamer since morrowind I try every fix and compare for the one I like most) leave the console stretched across the entire display RECT. That can be worked with but I prefer to have my Interface remain on the main panel as if I had only that one and allow the satellites to be peripheral display only.

Robert