[quote][quote][quote][quote][quote]I added helifax's fix to SVN and cleaned up a few things.
Download the new version (r394) from the Widescreen Fixer website. The newest Skyrim plugin is included so don't overwrite it with the files found in posts older than this one.
here is what i was missing!!!
Game page is written like the version posted there is the newest with auto-detect. but wasnt.
I've downlaoded r394 from the fixer website and left the plugins alone. However whenever I run the game it runs everytime on 3 independent screens. Not sure why this is occuring. My skyrimprefs file is correct and set to read only and I've tried r394 on both auto-detect and manual settings. The plugin auto-enablling is working fine though. If I use the r386 version with Helifax's 1.4.27.0.4 without the improvements added the game runs fine. I don't mind using the previous versions but I'm not sure why it won't run correctly with their latest fixes.
Exo
This is very weird indeed. The difference between the 2 versions is basically minimal, and has to do with some minor tweaks that couldn't change the behavior like that...
Yeah I can't figure it out yet but so long as no one else is having this problem I don't think there'e any real reason to figure it out because I'm fine using the first fix.
Just to confirm I'm using the right combination though I am using r386 with the plugin dated 2012-03-05 21:13 and this works fine. When I use download r394 it comes with the plugin dated 2012-03-06 11:28 and this is the combination that only displays the game individually on all 3 monitors. I have confirmed that WSF is detecting my correct resolution but for some reason it still loads on all 3 screens individually. Doesn't have any effect if I configure manually instead of auto-detect. I have confirmed all the other things I can think of such as the skyrimpref.ini file, and read only, etc and am confident this is all ok becuase the first plugin works fine with the first fix.
Since no one else seems to be having any issues I'm kinda convinced that the problem is probably caused by a mod. Unfortunately, I installed my first bunch of mods manually so it will take a clean install or some time to clean these all out to verify that. All the mods that I installed under Nexus Mod Manager have been disabled so it's probably an older mod I installed manually that is causing the problem. If i get time I'll go for a clean install and check it out and let people know in case they are having the same issue at some point.
Now that Mass Effect 3 is released I'll be distracted for a bit from Skyrim anyway. :) Thanks for working your Mass Effect fixes as well Helifax as I still have to finish ME2 tonight. When I get paid I'll send some love your way. However, unfortunately I won't be able to round up the $1K for a quicker Skyrim VI relase though. lol
EDIT: Oh dang, I bet I was dumb and started running r395. I'll have to check that when I get home.
Dopefish released a new PLUGIN FOR SKYRIM. There you can
configure the time for the automatic kick in. Try to increase it, or decrease it and see if that make a difference;)) I know...timeouts sux but was the only way I could make it automatically kick in;)) You can find it on the Official Site of WideScreen Fixer!
Hope this helps!!
Best Regards
Ok Helifax,
I figured out what's going on with r394 and r395 on my machine.
It seems that if the fix enables too soon the result is the game running on 3 screens independently. I timed how long it takes my game to run when I hit play on the Skyrim startup screen. It's close to 15 seconds before my movie comes up from the time WSF enables the fix. So In WSF I moved the slider to 7 seconds in r395. Then I tested hitting play on the skyrim menu and watied about 7 seconds before I started up WSF and the plugin. Once I did this, the fix kicked in after the movie started and everythign ran fine. I'm guessing the reason my game takes so long to load is I'm running and loading a lot of mods. So that's what's going on and why r386 with the manual enable runs fine on my machine and these don't. I am fine using the r386 but if anyone else runs into this at least we'll know what's going on.
Regards,
Exo