I got the game. Total nostalgia rush. Wondering if anyone knows of a way to run in Windowed Mode for streaming/recording? Doesn't appear to even allow you to alt-tab out.

Running Windows 8 if that helps.

Thanks.

Try using D3DWindower or DxWnd

http://community.pcgamingwiki.com/files/file/129-d3dwindower/
http://sourceforge.net/projects/dxwnd/

I don't have this game, so can't test it, but if you have a problem, you can also try posting on DxWnd forum - https://sourceforge.net/p/dxwnd/discussion/general/

Not sure if you can, or whether it would be any use if you could. PCGamingWiki reports that if the game loses focus then it will not regain focus and you'll have to kill the task. This happened to me when I tried to bring up the Task Manager to set single core affinity, so instead I had to create a shortcut to set the single core for me on loading the game up.

Actually, you can and D3DWindower works extremely well. Alt-tabbing is no problem (pauses the game), and it even works with nGlide.

I could write up a brief guide on using/combining all of these, if there's interest.

There may well be interest, and it would seem, then, that PCGamingWiki is out of date with this game.
By any chance, does D3DWindower fix the camera issue and mouse lag?

Also, I tried to use nglide tonight, but I like to run it portably by putting the dll files within the game folder (more for old DOS games really so that I can bundle the files in a single archive and move it to another computer without having to set it all up again, just extract and play). However, Rogue Squadron only detects the glide2x.dll file if it is in the Windows System32/SysWOW64 folder.

True, but once it detects it, I was able to move the file to the game folder, and it still ran. I'm not sure where the nGlide configuration is stored, so I can move that file too, uninstall and test. Also, not sure which of the other libraries may or may not be needed. Feel free to do your own tests and share the results. I share your affinity for portable installations, and can help you make a portable reg file for the game, too :-)

As for the mouse lag... it's not a bug I've experienced (or I've never noticed it). Again, try and see if it changes anything for you. The camera is still iffy. I remember experiencing this bug in the past, but forget what I was experimenting with, at the time. Another glide wrapper, perhaps?

See, that's what I tried to do, deleting the files from SysWOW64 (so that they were only in the ROGUE folder) after I'd chosen the Glide renderer in the setup utility, but on starting up the game it didn't kick off the 3DFX mode. :S

The nGlide configuration is saved in registry. It used to be stored in a file but I think around version 0.99 or 1.00 it moved to the registry. This has caused issues with GOG games in the past where different games come with different nGlide versions and the older versions use different values for their settings, so if you don't set it up each time you switch between the games you could end up with no display.

The mouse lag has been mentioned by some here in the GOG forums, but I don't know if it affects everyone. For me, when I move the mouse it is a good second or two before the reticule moves in that direction making it feel very sluggish. Joystick and keyboard respond immediately though, so the game is playable that way.

Lastly, I get the camera issue more with the A-Wing and Airspeeder as with those it sometimes happens even when I've pressed F1 to go to the close view camera. But with the X-Wing in close view it doesn't seem to happen. Maybe it is related to the craft speed as A-Wing is very fast?

The camera issue is a result of faulty code which zooms it out when you throttle up, so fast craft are more affected. Similarly, you can restore your view when you slam on the brakes.

I wrote up that guide, including instructions for portable nGlide. Check it out.

I've never had that issue with the mouse. Is it on every screen, just the menus, just the gameplay? Can it be Vsync related, either from in-game or forced through video driver?

Just had a read through of your guide. Seems pretty comprehensive. I do have some info on joysticks/controllers though. Will post them on your guide thread. :)

Sometimes, with the A-Wing, even slamming on brakes only brings the camera in a little closer, but it still feels very loose, not like a chase cam at all, not until I either cycle through camera modes or press F1. Trying to play A-Wings from within the cockpit now, but I'm missing the peripheral vision of the external camera.

The mouse only seems affected in-game. The menus are fine.

Any result playing around with Vsync? Also, do you have any special drivers for the mouse, or some program that runs in the background?

D3DWindower (and other similar tools) have settings for mouse behaviour, so you can try those, see if they work.

If I turn vsync off in the game video settings then I get delays in the hangar, the text scroll at the start of each chapter, and the screen wipe when skipping cutscenes. Makes no difference to the mouse in game though, so I've turned it back on.

My mouse is a Microsoft Sidewinder OEM, so uses the Intellipoint software.

Have you tried disabling/turning it off? I imagine you're using it for some custom button functionality, but if it has some smoothing or filtering options, they might be interfering with input. Also, I'm thinking that it may help if you try to force, one or both RS and IP to use different or the same core. No idea how two programs like these might interact on a multicore system.

The Intellipoint software allows me to set the three DPI settings and the two thumb buttons. It runs constantly whilst the PC is running. I disable mouse acceleration in Windows (that annoying enhance mouse pointer precision option).

Anyway, I just finished the game using my 360 controller via vJoy. Then I found out about the Home key for a real tight and close up external camera. Plays really nicely with that, no more camera falling behind. :)

I thought those DPI buttons had a set of firmware presets. Mine always have and work without any extra software. I can't really discount intellipoint being the culprit.

There are presets, but the Intellipoint software allows you to change them to your own preferences. Mine are 400, 1000, 1600.



Oh, I found a nice alternative to cockpit view to solve the camera issue. Press the Home button for the forward looking camera. It sits on the back of the starfighter so the camera never lags behind. It isn't quite the chase cam of F1, but it does give a wider field of view.