Yes, and the Gall Spaceport level is very hard to play in 60 fps. the character glides, and you fall to your death a lot

Same Problem. Makes it impossible to set keybindings.

You got a controller plug in? It does this with my xbox controller in, since the joystick is a little bit off center.

Most game ignore the dead zone but look like this game dont.

I think this should be marked as solved for the following solution:

You can edit the NVIDIA profile from 60 fps to 30fps to restore the speed of Dash to the normal N64 settings. The NVIDA profile can be found here:

C:\Program Files (x86)\GalaxyClient\Games\Star Wars - Shadows of the Empire\NVI

Run the inspector program, import the SHADOWS profile, and you can edit the settings. Click APPLY CHANGES and play the game; notice Dash runs at normal speed now.

I think the developers should make 30FPS the default and allow people to raise the FPS if desired.

I do have a wireless xbone controller. kind of need it working to bind its keys. I see what your saying though, thanks for the heads up!

Have you been able to map the trigger keys of the xbox controller? I can't get these keys to be recognized.

Yes I have the X box 360 wireless controller. The problem of the mouse cursor moving to the top of the screen does not occur if i start the game without the controller on - but then i can't use the controller...

I was able to map all the keys apart from the triggers - i had to keep the left analogue stick pushed down slightly to counteract the upwards movement, then could use the mouse to place the cursor where i wanted. Massive pain.

Fix this please GOG!

The update doesn't help in my case, it's still the same. That's no wonder however, as it was locked at 60 fps before. 60 fps seems to be too much for this game, 30 should be correct.

Here is a video showing the difference between too fast and normal, plus the fix.

1st half runs at 144fps, 2nd half 60fps.

Fix - Nvidia Control Panel - Manage 3D settings - Program Settings - Shadows of the Empire - Preferred Refresh Rate - set to 'Application Controlled'

Running on an Acer 144Hz G-sync monitor, GTX 970, Windows 10

https://youtu.be/WdkbC3iOsD8

That video was for the original GOG installer, and the fix being to limit to 60 FPS. GOG have since released two new versions of the installer since then, the first new version providing an Nvidia Inspector profile to apply the 60 FPS limit for you, the second new version (released today) for some other fix when using Shadows.exe instead of SOTE.exe or something like that.
My initial thoughts were that 30 FPS would be correct considering the age of the game, but on playing the GOG version game with the 60 FPS limit in place I've so far managed to play through all of part 1 and also the junkyard level ending with the boss fight with IG-88, and it all seemed fine. So I'm not yet sure.
The trigger keys on an Xbox 360 controller are an axis, because they are analog and the controller is XInput. In the XInput mode they are separate axes, but in DirectInput mode (which this old game would use as it was long before XInput showed up) the triggers are merged into a single axis (which has its own issues as both fully pressed is the same as both unpressed as they just cancel each other out). I'd imagine you can't map them in the game as it doesn't recognise the axis. Instead, try using Xpadder or Joy2Key to map the analog triggers to keys, and then map the desired functions to those same keys in the game settings.
The developers didn't provide the Nvidia Inspector profile for the game, GOG did, due to feedback in the forums on release of the game.

I've been playing at 60 FPS and been doing fine, but I've not tried 30 FPS yet.

If you think this needs changing then you need to raise this with GOG support and if they agree (or you provide evidence proving that it needs to be changed) then they may then release a new installer version with a new profile set at a 30 FPS limit.

A common issue with 360 controllers as they are XInput, and XInput games usually have settings for deadzone. In Windows you'll notice you can't set the deadzone for the controller as it is expected that games would have this setting.

As this game is old, and so using DirectInput, there is no deadzone setting it can use from the controller. But this can be fixed if you are willing to do some work. There's a program called XInput Plus that acts as a wrapper between the XInput controller and the DirectInput messages that get sent to the game. With XInput Plus you map your XInput controller to DirectInput equivalents, and you can even set deadzones and even make the round range of motion from the sticks into square (so that when the stick is at the NW position, say - using compass directions to describe the position - it is picked up in game as the top right corner, a further distance from centre than when it is at W or N).

The downside of XInput Plus, however, is that it doesn't have an english manual or website, and some of the options are not named how you would expect them to be, so it may take some playing around with it to get the desired effects.
I only half agree here. Old games often used hardware timers for physics and such (just look at Interstate '76) and so really, to keep them running as intended, the framerate should be limited to what the game was designed for.

Any thoughts about providing an Nvidia profile for I76, by the way - the profile with SotE was the first time I've seen you do this, and it's a great idea.

With Shadows of the Empire, though, I've not noticed any issues with 60 FPS yet, but I've not played at 30 FPS to compare, so I can't say what the correct framerate should be for the game.

Leave it at 60, its running great now - the updated installers fixed it for me without having to manually edit the nvidia profile like i showed in my comparison video.

Without reference it's hard to tell, the game is perfectly playable a 60FPS I think,

but if you compare with N64 version side by side in first level the up/down movement of the droid make it clear it was intended to be at 30FPS IMHO.