Flawless Widescreen

[funkyb]

How does one rollback to the prior version? I updated today after a 2 day gaming break and found FWS is no longer working with The Witcher 2... I just got to chapter 3 and can't bear to play the rest on a single screen

[Wijkert]

How does one rollback to the prior version? I updated today after a 2 day gaming break and found FWS is no longer working with The Witcher 2... I just got to chapter 3 and can't bear to play the rest on a single screen

With rollback I didn't mean I literally rollback to a previous version myself, but the rollback of SWIG 3.0.0 to 2.0.11 that Hayden did in the latest patch.

[HaYDeN]

Looks like there might still be issues for AMD users? [there always has been their drivers and API are subpar]

I don't have a AMD card so I can't easily test... but can someone confirm/deny?


Instead of people getting super angry sending emails - how about helping me help you... what does the status tab say about the detection of your card?

[kingcasper]

hey hayden..

im playing ds2 with amd card no issues i see ?

loading is slightly longer initially but could be my imagination


whats the issue specifically and ill see if i can check it out ?

[tapiro]

Looks like there might still be issues for AMD users? [there always has been their drivers and API are subpar]

I don't have a AMD card so I can't easily test... but can someone confirm/deny?


Instead of people getting super angry sending emails - how about helping me help you... what does the status tab say about the detection of your card?

Hello Hayden,

I was hoping you could help me (and possibly other AMD users). I've been trying to make Flawless Widescreen run on my rig in order to play Watch Dogs, but so far it's been a no go. Here is my config:

i7-3930k CPU
32GB 1600mhz DDR3 RAM
ASUS Rampage IV Extreme MB
AMD 6990 Display Adapter
5x1 Dell U2312HMt Displays (in portrait mode)
Windows 8.1 x64

My current desktop resolution is 5650x1920 (with bezel compensation).

I've tried both the latest version of Catalyst 14.6 and the previous one 14.4, but the x64 version of Flawless Widescreen crashes for me at launch. It runs fine when Catalyst is not installed and it's picking up the generic Microsoft AMD driver, but not when Catalyst is installed. The x86 version works fine though (but I can't use that for Watch Dogs which, as you know is x64 only).

Here is what I see in the event viewer regarding the app crash:


Faulting application name: FlawlessWidescreen.exe, version: 1.0.0.12, time stamp: 0x5291d607
Faulting module name: atiadlxx.dll, version: 6.14.10.1300, time stamp: 0x53507b40
Exception code: 0xc0000005
Fault offset: 0x00000000000138cb
Faulting process id: 0x18d8
Faulting application start time: 0x01cf7b39a8d83c81
Faulting application path: I:\Desktop\flawlesswidescreen\FlawlessWidescreen.exe
Faulting module path: C:\Windows\SYSTEM32\atiadlxx.dll
Report Id: e695c939-e72c-11e3-82d7-5404a638259b
Faulting package full name:
Faulting package-relative application ID:

Here is the settings.xml that's generated after the first run with the x86 version (i'm attaching this because I see it's picking up a wrong resolution for my rig, and I'm not sure whether it might be relevant to your troubleshooting):

<?xml version="1.0"?>
<Configuration Schema="1.0">
<StartupSettings>
<StartupPosition Position_X="-1" Position_Y="-1" RememberPosition="false"/>
<StartupState FirstUse="false" 1010_FirstUse="false" LicenceAgreed="true" StartMinimized="false" StartWithWindows="false" StartUpdateCheck="true"/>
</StartupSettings>
<Steam_Origin_Detection Steam_Path="\steam\;\steamapps\" Origin_Path="\origin games\;\origin\"/>
<AppState CompactMode="false">
<OpenViewports>
<Viewport PluginNameSpace="FWS_Plugins" ModuleNameSpace="WatchDogs" Focus="true"/>
</OpenViewports>
</AppState>
<DisplayDetectionSettings>
<HardwareOptions NVIDIADetection="true" AMDDetection="true" GenericDetection="true" SoftTHDetection="true"/>
<AssumptionSettings Enabled="true" BCEnabled="false" Width="2561" Height="1000" DisplaysX="3" DisplaysY="1" SafeZoneX="5" SafeZoneY="0"/>
<CustomSettings Enabled="false" Width="5760" Height="1080" DisplaysX="3" DisplaysY="1" HUDWidth="1920" HUDHeight="1080" HUDX="1920" HUDY="0"/>
</DisplayDetectionSettings>
<UpdateSettings>
<CoreUpdate AutoCheck_Updates="true" AutoInstall_Updates="true" BETAOptIn="false" LastUpdateCore="1401365833" UpdateCoreFreq="1"/>
<PluginUpdate AutoCheck_PluginUpdates="true" AutoInstall_PluginUpdates="true" AutoInstall_MissingDeps="true" LastUpdatePlugins="1401365833" UpdatePluginsFreq="2"/>
<RepositoryUpdate AutoCheck_NewPlugins="true" AutoInstall_NewPlugins="false" LastUpdateRepo="1401365833" UpdateRepoFreq="1"/>
<Repositorys/>
</UpdateSettings>
<HotkeySettings EnableToggle="1626" IncreaseFOV="107" DecreaseFOV="109"/>
</Configuration>

I'm really baffled by this issue cause the way it looks from my perspective, it would seem that every AMD user would have to incur in such a problem, but since I don't see anyone complaining about it, it makes me wonder if there's something wrong with my rig, aside from the inability to run your app. I should mention I'm not running any AV, including Windows Defender, which is deactivated.

I had a chance to try version 1.0.12, 1.0.13 and 1.0.14 of your app but the results are always the same. The x86 versions of the aforementioned work, the x64 crash on start. They all work fine when Catalyst is not installed as well. So, bottom line, when atiadlxx.dll is installed, the 64 bit version of Flawless Widescreen is not running for me.

On a side note, would Flawless Widescreen adjust the AR according to my specs anyway?
I run the game at 4708x1600, which gives me ~38fps right now (with Xfire disabled); hopefully that should increase further once AMD releases better drivers (so I can really use Xfire which at the moment works with the latest and the previous versions of Catalyst, but actually halves the performance when compared to single card usage, rather then double it) and most importantly Ubisoft does his homework and optimize the game properly.

I hope you'll be able to figure out what the problem is, or at least point me in the right direction as to where to look for a culprit.

Thanks in advance!

[funkyb]

Looks like there might still be issues for AMD users? [there always has been their drivers and API are subpar]

I don't have a AMD card so I can't easily test... but can someone confirm/deny?


Instead of people getting super angry sending emails - how about helping me help you... what does the status tab say about the detection of your card?

I'm sure you've figured this out already but I'm who you worked with on steam and the modified version we tested did work. Many thanks for your help and feel free to contact me if you ever need an AMD tester. My apologies for not including the status screenshots or more config info in my original post; I code and should know better than that =P

[hexenaci]

Also have to say thanks for all your work and everything you do. Specifically made this account to tell you that you're made of awesome! You're the only reason I'm able to play several titles in eyefinity, and actually have it be a positive instead of a negative experience.

shittycode 1: you hear about that guy?
shittycode 2: that hayden guy? yeah OP




Am an AMD user though and still having issues with skyrim

Just hangs while FWS says configuring. The Skyrim window is immediately non responsive upon opening.

Currently running 2X AMD 6950's in eyefinity.

[tapiro]

Looks like there might still be issues for AMD users? [there always has been their drivers and API are subpar]

I don't have a AMD card so I can't easily test... but can someone confirm/deny?


Instead of people getting super angry sending emails - how about helping me help you... what does the status tab say about the detection of your card?

Hello Hayden,

I was hoping you could help me (and possibly other AMD users). I've been trying to make Flawless Widescreen run on my rig in order to play Watch Dogs, but so far it's been a no go. Here is my config:

i7-3930k CPU
32GB 1600mhz DDR3 RAM
ASUS Rampage IV Extreme MB
AMD 6990 Display Adapter
5x1 Dell U2312HMt Displays (in portrait mode)
Windows 8.1 x64

My current desktop resolution is 5650x1920 (with bezel compensation).

I've tried both the latest version of Catalyst 14.6 and the previous one 14.4, but the x64 version of Flawless Widescreen crashes for me at launch. It runs fine when Catalyst is not installed and it's picking up the generic Microsoft AMD driver, but not when Catalyst is installed. The x86 version works fine though (but I can't use that for Watch Dogs which, as you know is x64 only).

Here is what I see in the event viewer regarding the app crash:


Faulting application name: FlawlessWidescreen.exe, version: 1.0.0.12, time stamp: 0x5291d607
Faulting module name: atiadlxx.dll, version: 6.14.10.1300, time stamp: 0x53507b40
Exception code: 0xc0000005
Fault offset: 0x00000000000138cb
Faulting process id: 0x18d8
Faulting application start time: 0x01cf7b39a8d83c81
Faulting application path: I:\Desktop\flawlesswidescreen\FlawlessWidescreen.exe
Faulting module path: C:\Windows\SYSTEM32\atiadlxx.dll
Report Id: e695c939-e72c-11e3-82d7-5404a638259b
Faulting package full name:
Faulting package-relative application ID:

Here is the settings.xml that's generated after the first run with the x86 version (i'm attaching this because I see it's picking up a wrong resolution for my rig, and I'm not sure whether it might be relevant to your troubleshooting):

<?xml version="1.0"?>
<Configuration Schema="1.0">
<StartupSettings>
<StartupPosition Position_X="-1" Position_Y="-1" RememberPosition="false"/>
<StartupState FirstUse="false" 1010_FirstUse="false" LicenceAgreed="true" StartMinimized="false" StartWithWindows="false" StartUpdateCheck="true"/>
</StartupSettings>
<Steam_Origin_Detection Steam_Path="\steam\;\steamapps\" Origin_Path="\origin games\;\origin\"/>
<AppState CompactMode="false">
<OpenViewports>
<Viewport PluginNameSpace="FWS_Plugins" ModuleNameSpace="WatchDogs" Focus="true"/>
</OpenViewports>
</AppState>
<DisplayDetectionSettings>
<HardwareOptions NVIDIADetection="true" AMDDetection="true" GenericDetection="true" SoftTHDetection="true"/>
<AssumptionSettings Enabled="true" BCEnabled="false" Width="2561" Height="1000" DisplaysX="3" DisplaysY="1" SafeZoneX="5" SafeZoneY="0"/>
<CustomSettings Enabled="false" Width="5760" Height="1080" DisplaysX="3" DisplaysY="1" HUDWidth="1920" HUDHeight="1080" HUDX="1920" HUDY="0"/>
</DisplayDetectionSettings>
<UpdateSettings>
<CoreUpdate AutoCheck_Updates="true" AutoInstall_Updates="true" BETAOptIn="false" LastUpdateCore="1401365833" UpdateCoreFreq="1"/>
<PluginUpdate AutoCheck_PluginUpdates="true" AutoInstall_PluginUpdates="true" AutoInstall_MissingDeps="true" LastUpdatePlugins="1401365833" UpdatePluginsFreq="2"/>
<RepositoryUpdate AutoCheck_NewPlugins="true" AutoInstall_NewPlugins="false" LastUpdateRepo="1401365833" UpdateRepoFreq="1"/>
<Repositorys/>
</UpdateSettings>
<HotkeySettings EnableToggle="1626" IncreaseFOV="107" DecreaseFOV="109"/>
</Configuration>

I'm really baffled by this issue cause the way it looks from my perspective, it would seem that every AMD user would have to incur in such a problem, but since I don't see anyone complaining about it, it makes me wonder if there's something wrong with my rig, aside from the inability to run your app. I should mention I'm not running any AV, including Windows Defender, which is deactivated.

I had a chance to try version 1.0.12, 1.0.13 and 1.0.14 of your app but the results are always the same. The x86 versions of the aforementioned work, the x64 crash on start. They all work fine when Catalyst is not installed as well. So, bottom line, when atiadlxx.dll is installed, the 64 bit version of Flawless Widescreen is not running for me.

On a side note, would Flawless Widescreen adjust the AR according to my specs anyway?
I run the game at 4708x1600, which gives me ~38fps right now (with Xfire disabled); hopefully that should increase further once AMD releases better drivers (so I can really use Xfire which at the moment works with the latest and the previous versions of Catalyst, but actually halves the performance when compared to single card usage, rather then double it) and most importantly Ubisoft does his homework and optimize the game properly.

I hope you'll be able to figure out what the problem is, or at least point me in the right direction as to where to look for a culprit.

Thanks in advance!

Just an update on my situation: I actually fixed the crash! It turns out the culprit was indeed in the automagically generated settings.xml. I manually input it, changing the following:

<CustomSettings Enabled="true" Width="5650" Height="1920" DisplaysX="5" DisplaysY="1" HUDWidth="1920" HUDHeight="1080" HUDX="1920" HUDY="0"/>

and I got no more crashes. I also tested with Watch Dogs and it does what it's supposed to, great (http://imgur.com/AvdL3Dy,60rhYIK)!

On the other hand, I tried The Amazing Spiderman 2 (which I've also kept in the back-burner since eyefinity is a no go) but I'm getting some pretty weird result (http://i.imgur.com/NlhD2Wj.jpg). Any chance this can be fixed?

Cheers

[MobsterOO7]

... what does the status tab say about the detection of your card?

I hope I'm copying the right one but mine says: "Display Detection | Found AMD device: AMD Radeon HD 6900 series". I hope that helps!

[HaYDeN]

People having issues need to upgrade to 1.0.15 - all the engine related stuff should now be fixed in 1.0.15, start Flawless WIdescreen - then take a screenshot of the status.



I want to see the display detection breakdown, eg. how it detected your display along with what your setup actually is (eg. cards and number of screens)

If it crashes on launch, you could try editing the settings file....

Code: Select all

<DisplayDetectionSettings>
<HardwareOptions NVIDIADetection="true" AMDDetection="false" GenericDetection="true" SoftTHDetection="true"/>
<AssumptionSettings Enabled="true" BCEnabled="false" Width="2561" Height="1000" DisplaysX="3" DisplaysY="1" SafeZoneX="5" SafeZoneY="0"/>
<CustomSettings Enabled="false" Width="5760" Height="1080" DisplaysX="3" DisplaysY="1" HUDWidth="1920" HUDHeight="1080" HUDX="1920" HUDY="0"/>
</DisplayDetectionSettings>

eg. AMDDetection="false", and see if that gets rid of the crash.

What i found with FunkyB is that it works fine, if its only 3 monitors, if there's 4 monitors eyefinity detection breaks, there might also be issues with people in crossfire.

At this stage, a single card, with a single large display is confirmed to be working correctly.

[hexenaci]

Thanks hayden! Last little update fixed the issue for me! I can again rule the lands of Skyrim!

Just for reference, I do run a quad monitor setup: 3 monitors in eyefinity and one 65" LED above.

n00b fact: Catalyst control lets users create profiles and you can disconnect/turn off certain displays for specific profiles. Anyone having issues with quad setups, I'd recommend creating a profile that disables your fourth screen, as I've never ran into issues.

Thanks again Hayden

[stoneeyelid]

I can't get Ghost 3.12.112 to work with the latest version of FWS 1.0.15 ... The fix won't enable and I get the below message...

"Configure function call for the attached process failed, retrying in seconds. Last Error: Could not find DefaultAspectRatio injection point, call of Duty; Ghosts may have updated to a version that is no longer supported. Try restarting Call of Duty: Ghosts or selecting a different version and re-enabling the fix. "

I've uninstalled 1.0.15 and installed 1.0.12 without letting it update and had the same issue. I've attached two .jpg files. One being FWS without the Ghost Plugin loaded and Steam not running. The second is a Post Ghost Plugin with both steam and Ghosts running.

I'm running Win7 x64, single AMD 7990 with three HP LP2065 1600 x 1200 monitors. AMD Catalyst Version is 14.4.

Any ideas?

[HaYDeN]

I can't get Ghost 3.12.112 to work with the latest version of FWS 1.0.15 ... The fix won't enable and I get the below message...

Fixed, they changed a flag on the EXE, now it's auto detected - somewhat unusual change.

Original:

Code: Select all

   if Process_EXEName == "iw6mp64_ship.exe" then MemoryPermissions = PAGE_EXECUTE_READWRITE or PAGE_EXECUTE_READ end
   if Process_EXEName == "iw6sp64_ship.exe" then MemoryPermissions = PAGE_EXECUTE_READWRITE or PAGE_EXECUTE_READ end

New:

Code: Select all

   MemoryPermissions = HackTool:GetMemProtect(HackTool:GetBaseAddress())

[stoneeyelid]

Thank you very much, Hayden!

[kingcasper]

are u the only person who works on your app hayden ??

how does someone learn to do it ? any tips.. id love to be able to help at some point

[Ufolog]

Greetings to you Master of Aspect!
Display detection fails to detect my setup



I can play WatchDogs only if custom override is selected

Actual settings are: HD7990 5916x1080 14.6 Cat. Samsung MD230x3 connected on 3 Displayports.
If you need any additional info from my "red corner" just let me know...
Thank you.

[chriswsgf]

Hello Hayden,

First thanks for your amazing work, been using this tool since i went for 21:9 monitor.

Problem i'm having right now is with Witcher 2, when i try to launch it (3.4.0 gog) the flawless widescreen app goes from fix enabled to disabled saying this :

Configure function call for the attached process failed, retrying in 54 seconds...

Last Error:
Could not find Resolution injection point, The Witcher 2 may have updated to a version that is no longer supported.

Try restarting The Witcher 2 or selecting a different version and re-enable the fix.

Any ideas?

[teardropmina]

hello
can't get flawless widescreen to update and install plugins at the moment/ for a while~

and I checked the website (flawlesswidescreen.org) and it said it's an Apache 2 Test Page~

are both the website and updating serivce down now?

thanks

[TheDestroyer]

Looks like the site is back up.

[HaYDeN]

My hosting provider is pissing me round, the particular IP fws is hosted on appears to be getting routed elsewhere periodically sometimes for multiple hours, because it's intermittent everytime they look at it it's conveniently working fine.