Widescreen Gaming Forum

Yes, patch broke it.

@ Work at the moment, but I will take care of it when I get home most likely.

New Changes: (30/07/2012)

- Updated Tribes Ascend for v1.0.1055.*
- Added new module, Orcs Must Die 2
- Added new module, Inversion

Massive thanks Hayden, Inversion works perfectly, also its a pretty rad game.

New Changes: (31/07/2012)

- Updated Skyrim for v1.7.7.0
- Updated Orcs Must Die 2 for Full Version

Also: I hear you on Inversion Sh4dowKing - it must be a issue with non 16:9 (eg. 5760x1080) based resolutions.... as it's working for valcan_s? Can't promise I'll get to it tonight however.

New Changes: (31/07/2012)

- Updated Skyrim for v1.7.7.0
- Updated Orcs Must Die 2 for Full Version

Also: I hear you on Inversion Sh4dowKing - it must be a issue with non 16:9 (eg. 5760x1080) based resolutions.... as it's working for valcan_s? Can't promise I'll get to it tonight however.

Yes iam playing on 16:10 with a res of 5040x1050 so that is the issue maybe you can make a fix for other aspect rations if you have time.

[quote]New Changes: (31/07/2012)

- Updated Skyrim for v1.7.7.0
- Updated Orcs Must Die 2 for Full Version

Also: I hear you on Inversion Sh4dowKing - it must be a issue with non 16:9 (eg. 5760x1080) based resolutions.... as it's working for valcan_s? Can't promise I'll get to it tonight however.

Yes iam playing on 16:10 with a res of 5040x1050 so that is the issue maybe you can make a fix for other aspect rations if you have time.

Find line 404 in (assuming default install) in "C:Program Files (x86)Flawless WidescreenPluginCacheFWS_PluginsInversionDependenciesScriptsInversion_UI.lua" - Open it in something like Notepad++ otherwise it will look like a big pile of text with no carrage returns.

Change "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt(DisplayInfo:GetiOffsetX(0))" to "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt( (DisplayInfo:GetWidth()/2) - (1920 /2) )"

And tell me if that fixes or alleviates the problem.... otherwise you can change to a static value, eg. "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt( 1800 )"

It would be nice to know what the value is that "looks right"

[quote][quote]New Changes: (31/07/2012)

- Updated Skyrim for v1.7.7.0
- Updated Orcs Must Die 2 for Full Version

Also: I hear you on Inversion Sh4dowKing - it must be a issue with non 16:9 (eg. 5760x1080) based resolutions.... as it's working for valcan_s? Can't promise I'll get to it tonight however.

Yes iam playing on 16:10 with a res of 5040x1050 so that is the issue maybe you can make a fix for other aspect rations if you have time.

Find line 404 in (assuming default install) in "C:Program Files (x86)Flawless WidescreenPluginCacheFWS_PluginsInversionDependenciesScriptsInversion_UI.lua" - Open it in something like Notepad++ otherwise it will look like a big pile of text with no carrage returns.

Change "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt(DisplayInfo:GetiOffsetX(0))" to "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt( (DisplayInfo:GetWidth()/2) - (1920 /2) )"

And tell me if that fixes or alleviates the problem.... otherwise you can change to a static value, eg. "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt( 1800 )"

It would be nice to know what the value is that "looks right"

Wow thank you hayden. I have followed your steps and i got it working. The first value "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt( (DisplayInfo:GetWidth()/2) - (1920 /2) )" did it. the HUD is centered now.

The second value "HUDFix:GetSubOffset("ValHUDLeft"):WriteInt( 1800 )" brings it more to the right ( more then it was). So iam happy that its solved now and iam thankfull for your time! :D

Borderlands issue:

As already mentioned in this thread, Borderlands crashes after 14 minutes. This is sad, as it is a really nice game, but the default view just sucks.

Crash has something to do with the MSVCR90.dll, the Visual C++ thig there i don't really know.

Anyway ...
Following thing seem to work:
Close flawlesswidescreen program, wait a minute, start it again, play another 14 minutes ... or longer (the second time it actually didn't crash for about 35min.

Awesome work, nonetheless!

Borderlands issue:

As already mentioned in this thread, Borderlands crashes after 14 minutes. This is sad, as it is a really nice game, but the default view just sucks.

Crash has something to do with the MSVCR90.dll, the Visual C++ thig there i don't really know.

Anyway ...
Following thing seem to work:
Close flawlesswidescreen program, wait a minute, start it again, play another 14 minutes ... or longer (the second time it actually didn't crash for about 35min.

Awesome work, nonetheless!

Have you already tried to re-install Microsoft Visual C++??

Just go to add/remove list and uninstall all the Microsoft Visual C++ you have and download the newest one. (microsoft visual c++ 2010)

Still looking for a solution to my Skyrim's 'Large Inventory Pics' when I run Flawless Widescreen, SKSE and SkyUI??? Is anyone else running Flawless, the SKSE plug-in and the SkyUI mod?? Just wondering if there's a known conflict....Thank you.

Attached files

Still looking for a solution to my Skyrim's 'Large Inventory Pics' when I run Flawless Widescreen, SKSE and SkyUI??? Is anyone else running Flawless, the SKSE plug-in and the SkyUI mod?? Just wondering if there's a known conflict....Thank you.

Last I checked the WideScreen Fixer plugin didn't have any problems with SKSE and SkyUI...but I might be lying out of miss-information...

Hi,

I'm having a problem starting Flawless Widescreen since I updated to version 12.6 of Catalyst.

The only other reference to the problem I've found is here - http://www.wsgf.org/forum/forums/gaming/requestdiscuss-game-solutions/18156/skyrim-multi-monitor-user-interface-fix-disc?page=286#comment-247560

I get the following report:
Problem Event Name: APPCRASH
Application Name: FlawlessWidescreen.exe
Application Version: 1.0.0.6
Application Timestamp: 4ffb06bc
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.7601.17744
Fault Module Timestamp: 4eeaf722
Exception Code: c0000005
Exception Offset: 000097e9
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

msvcrt.dll is part of the C++ package so I tried uninstalling and re-installing it. I've completely uninstalled all AMD drivers, including registry, and re-installed all to no avail.

Any ideas on what the issue might be?

Edit:
I just uninstalled Flawless Widescreen and all AMD drivers again. I rebooted and installed Flawless Widescreen without installing any Catalyst. Flawless Widescreen runs under this scenario. I'll try installing an older version of Catalyst (11.12) and see how I go.

Edit:
Installed 11.12 of Catalyst (anything 12.x causes me many BSOD rage moments) and tried running Skyrim. Flawless Widescreen detected the running process but doesn't apply the fix correctly. I still get 3 individual screens, but the mouse is really slow. So it's like the mouse sensitivity was applied, but not the widescreen adjustment.

I think I've gone as far as I can. Any ideas what I can do next?

Not sure what's causing your problem, but just thought I'd say I've not had this with a 5870 while running 12.6 beta (and now 12.7 beta), but I don't think I ever ran the actual 12.6 release. I can't imagine you'd get a different result on a beta of the same version (unless something relevant changed of course), but if you don't mind some more potential headaches the new beta might be worth a try. Runs very well for me.

Hi,

I'm having a problem starting Flawless Widescreen since I updated to version 12.6 of Catalyst.

The only other reference to the problem I've found is here - http://www.wsgf.org/forum/forums/gaming/requestdiscuss-game-solutions/18156/skyrim-multi-monitor-user-interface-fix-disc?page=286#comment-247560

I get the following report:
Problem Event Name: APPCRASH
Application Name: FlawlessWidescreen.exe
Application Version: 1.0.0.6
Application Timestamp: 4ffb06bc
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.7601.17744
Fault Module Timestamp: 4eeaf722
Exception Code: c0000005
Exception Offset: 000097e9
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 3081
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

msvcrt.dll is part of the C++ package so I tried uninstalling and re-installing it. I've completely uninstalled all AMD drivers, including registry, and re-installed all to no avail.

Any ideas on what the issue might be?

Edit:
I just uninstalled Flawless Widescreen and all AMD drivers again. I rebooted and installed Flawless Widescreen without installing any Catalyst. Flawless Widescreen runs under this scenario. I'll try installing an older version of Catalyst (11.12) and see how I go.

Edit:
Installed 11.12 of Catalyst (anything 12.x causes me many BSOD rage moments) and tried running Skyrim. Flawless Widescreen detected the running process but doesn't apply the fix correctly. I still get 3 individual screens, but the mouse is really slow. So it's like the mouse sensitivity was applied, but not the widescreen adjustment.

I think I've gone as far as I can. Any ideas what I can do next?

Ernfinkle, Thanks for taking the time to investigate what you have.

Please can you try http://www.flawlesswidescreen.org/FlawlessWidescreen.exe - replace your existing EXE in c:program files (x86)flawless widescreen.

it will pop up a message box at various steps through the c_DisplayDetection::DetectAMDHardware() function in Flawless Widescreen, if you can tell me the last messagebox and the message before it crashes/stops/dies etc then I can likely figure out which function call is causing the problem.... the new EXE may even just work because it does have some bug fixes not in the current public build.

I do still have my HD5870 lying around I can put back in the machine but it's a monstrous effort shifting all the cables around etc because they have different outputs (HDMI/DVI/DP etc)

Just downloaded a new free to play FPS bulletrun and i really like the game but the game has the same issue as blacklight: retribution. The fov is way to zoomed in on a multi-mon resolution. Hayden can you please fix this when you have time?

If you havent played this game yet its really funny and a great online Free to play shooter.

[quote]Borderlands issue:

As already mentioned in this thread, Borderlands crashes after 14 minutes. This is sad, as it is a really nice game, but the default view just sucks.

Crash has something to do with the MSVCR90.dll, the Visual C++ thig there i don't really know.

Anyway ...
Following thing seem to work:
Close flawlesswidescreen program, wait a minute, start it again, play another 14 minutes ... or longer (the second time it actually didn't crash for about 35min.

Awesome work, nonetheless!

Have you already tried to re-install Microsoft Visual C++??

Just go to add/remove list and uninstall all the Microsoft Visual C++ you have and download the newest one. (microsoft visual c++ 2010)

Of course i reinstalled 2005 and 2008, the ones Borderlands need. I didn't reinstalled 2010 yet. In the expanded errormessage it also does only mention the 2008 Version.

Did it fix it for you? I'd really like to know.
Because there are more ppl in this thread who have the same exact problem with Borderlands crashing after exactly the same time.

[quote][quote]Borderlands issue:

As already mentioned in this thread, Borderlands crashes after 14 minutes. This is sad, as it is a really nice game, but the default view just sucks.

Crash has something to do with the MSVCR90.dll, the Visual C++ thig there i don't really know.

Anyway ...
Following thing seem to work:
Close flawlesswidescreen program, wait a minute, start it again, play another 14 minutes ... or longer (the second time it actually didn't crash for about 35min.

Awesome work, nonetheless!

Have you already tried to re-install Microsoft Visual C++??

Just go to add/remove list and uninstall all the Microsoft Visual C++ you have and download the newest one. (microsoft visual c++ 2010)

Of course i reinstalled 2005 and 2008, the ones Borderlands need. I didn't reinstalled 2010 yet. In the expanded errormessage it also does only mention the 2008 Version.

Did it fix it for you? I'd really like to know.
Because there are more ppl in this thread who have the same exact problem with Borderlands crashing after exactly the same time.

I dont like the game very much so never played it but i tought u didn't re-install C++ already. Have you played longer without the widescreen fixer? Because if the game don't crash without the widescreens fixer then it should be an issue with the fixer.

Ernfinkle, Thanks for taking the time to investigate what you have.

Please can you try http://www.flawlesswidescreen.org/FlawlessWidescreen.exe - replace your existing EXE in c:program files (x86)flawless widescreen.

it will pop up a message box at various steps through the c_DisplayDetection::DetectAMDHardware() function in Flawless Widescreen, if you can tell me the last messagebox and the message before it crashes/stops/dies etc then I can likely figure out which function call is causing the problem.... the new EXE may even just work because it does have some bug fixes not in the current public build.

I do still have my HD5870 lying around I can put back in the machine but it's a monstrous effort shifting all the cables around etc because they have different outputs (HDMI/DVI/DP etc)

Thanks for the help Hayden.

The very last message is 'FreeLibrary(hDLL);'

When I started the game I got the Skyrim logo in the centre of each screen, but smaller this time, and no menu text. When I Alt-tabbed back to the desktop the debug messages appeared again and each time the last one was the same as above.

It stopping on FreeLibrary and the rest of the calls succeeding doesn't make any sense. I suspect it's heap/stack corruption, that's the lovely thing about c++ .. fuck the stack and it will just potentially keep executing for sometime before it crashes, masking the real culprit. (probably memory allocation/deallocation)

I'll probably have to put a AMD card back in a debug it, AMD have clearly changed something.

Hayden, if you're still looking to beef up the fix list, a fix for the original Far Cry never came to light. I tried the single-screen hor+ fix, but it only works until you aim through sight, then it gets messed up for good :(

One of my favourite games, and if I was ever able to play it on proper multi-monitor, I just may defecate masonry.

Teaser for my first hack (nearing completion - just a few things to figure out before I send it for review...namely the locations of all the hard coded FoV's (why R* why!?)...and hoping I don't miss any).

Attached files