SeamanStaines
04-30-10, 11:07 PM
Hello all,
Posted this on ubi forum but no answers yet...
I've been happily playing SH3/GWX on my old laptop with win7x86 at 1920x1200.
Recently bought an asus g73 which has win7x64 and i've setup SH3/GWX to play at 1920x1080. Running ati10.4 drivers.
All is going fine, until i run into enemy ship, get into position to attack, raise the periscope (using Ctrl PGUP) and as soon as i click the mouse ANYWHERE on the periscope screen...the mouse snaps/jumps to the FIRE button on screen and clicks it instead. Torpedo away. Bye bye element of surprise. And it keeps happening...if i try and click the LOCK button, or click to move the crosshairs in the periscope...then if there is a torp loaded in the currently selected tube...it gets launched.
So the only thing i had configured myself (other than setting res to 1920x1080) was the Numpad* key to instantly get back to 1024x time compression.
But i have since removed the line (Key1=0x6A,R,"Npad *") from my cfg thinking that maybe it caused my trigger happy mouse problem.
I dont think it did, cause the trigger happy mouse is still there.
Have i messed up my cfg file, or done something else silly ?
Posted this on ubi forum but no answers yet...
I've been happily playing SH3/GWX on my old laptop with win7x86 at 1920x1200.
Recently bought an asus g73 which has win7x64 and i've setup SH3/GWX to play at 1920x1080. Running ati10.4 drivers.
All is going fine, until i run into enemy ship, get into position to attack, raise the periscope (using Ctrl PGUP) and as soon as i click the mouse ANYWHERE on the periscope screen...the mouse snaps/jumps to the FIRE button on screen and clicks it instead. Torpedo away. Bye bye element of surprise. And it keeps happening...if i try and click the LOCK button, or click to move the crosshairs in the periscope...then if there is a torp loaded in the currently selected tube...it gets launched.
So the only thing i had configured myself (other than setting res to 1920x1080) was the Numpad* key to instantly get back to 1024x time compression.
But i have since removed the line (Key1=0x6A,R,"Npad *") from my cfg thinking that maybe it caused my trigger happy mouse problem.
I dont think it did, cause the trigger happy mouse is still there.
Have i messed up my cfg file, or done something else silly ?