Hard Light Productions Forums
General FreeSpace => FreeSpace & FreeSpace Open Support => Topic started by: Zamfire on November 16, 2014, 02:15:57 am
-
I cannot move my mouse to the bottom or right hand side of the screen when I enter the game. It hits an invisible wall and I can't even click on the very first button to get into the game. (Pressing enter works, but the problem is the same on the next screen, in the hangar)
I have scoured the internet and the only place that resembles anything close to an answer is Interplay's website, and their suggestion doesn't work, which is:
Q: My mouse is not working on the bottom or right hand side of the screen.
A: This can happen if your games resolution is set to a different resolution than that of Windows. You will want to go into your display properties in Windows and make sure that it is set to the same setting you selected for the game.
(http://www.interplay.com/games/support.php?id=131#5)
I have used both the most up to date wxlauncher and FS2 Open Launcher 5.5. Neither of these fixes the problem. If I change my computer's resolution to something much lower (1024x768) and then change the game's resolution to match that, then I can only see the upper left hand side of the screen. The same sized box that my mouse was in before. The arrow button on the select player screen is completely gone off the screen. If that makes sense.
Anyways, I have been working on this for hours so forgive me if I don't respond to you until tomorrow, I am going to bed.
If anyone can help me with this, I would be most grateful.
-
This appears to happen every now and then, and shouldn't cause that much trouble during actual game time, just during the menu. It may be that the window is not getting full focus from the OS, so try Alt-Tabbing to the desktop and then back to the game to see if that does anything.
If not, then Please post your fs2_open.log file. Instructions on how to do this can be found in this post.
Also, what OS are you using?
-
Thank you so much for responding z64555.
As soon as I saw your post I jumped out of bed to try alt-tabbing, sadly, that did not work.
I am running windows 8.1 64
16 Gigs of RAM,
nVidea 760
i5
Anyways, attached is fs2_open.log.
[attachment kidnapped by pirates]
-
This sounds a bit like http://www.hard-light.net/forums/index.php?topic=88527.0 . Use wxLauncher as the old Launchers don't work under Win8. And run it as an admin when setting your resolution. The log says that FSO is running at 640 x 480 with 16-bit colors so there's some resolution crap going on and that is probably why you're hitting a wall caused by that low resolution on the interface.
-
Sadly, that did not work, BUT I did find a work around.
I added the tag: -res 1280x700 and put it in windowed mode. It fills up pretty much the entire screen. (adding a few pixels will fill it out, I will fine tune it later.)
Anyways I guess this is now resolved, kind of. If anyone else has this problem, may God have mercy on your soul.
-
How strange! I'm running on Windows 8.1 and have gotten that issue before, but it has since been resolved by using wxLauncher instead of the old 5.5g.
Do you think maybe somewhere it's running it in compatibility mode?
-
What is comparability mode? Did you mean compatibility?
-
Yes, compatibility. My spelling has been on the decline for years. :(
-
I have the same exact issue. My mouse cursor can not move to the whole screen.
I run the launcher in admin mode aswell.
I tried with the resolution at the end of the command line and without it. I tired several resolutions. Always the same problem.
Any help welcome.
Thank you
V
[attachment deleted by admin]
-
I have had this fault, turned out to be a DPI setting in the desktop scaling was the problem. The desktop wasn't set to 100% but something like 125% or something. Switching the DPI/Scaling on the desktop back to defauly 100% solved the issue!
Hope this reply helps
Better than playing in full screen windowed mode.
-
There's an option in compatibility mode settings (right-click the .exe > properties) to disable scaling on High DPI settings for just that program.
-
The dpi scaling of the desktop was indeed the issue and disabling it for that specific .exe as suiggested solved it.
Thank you very much for your help.
Cheers,
K