It is strongly recommended that you try to run the game without any compatibility options and with VSync ON.

If your game is running extremely fast, with sound at normal speed and lagging behind the animations, try this fix.

NOTE: Rogue squadron is a fairly old 3D game that uses DirectX-6-era graphical calls to D3D and DirectDraw. These will often be incompatible with modern drivers and hardware and may result in the game not working. Since nGlide translates the game's older graphical routines to more modern ones, using the program may solve some problems people are having with the original D3D renderer.

High Resolutions and Framerate through Glide Emulation:

To get this working, you will need to download and install nGlide 1.04 (Note: 1.03 causes crashes, while 1.02 does not)

Run the nGlide configuration utility and configure how you wish to run the game.
- Set the resolution to your monitor's native one (or another, if you wish), unless you want to run the game in a window (see below)
- Set the Aspect Ratio to 4:3
- Set the Refresh Rate to your monitor's native one (or another, if you wish)
- Set Vertical Synchronisation to On (Default)
Leave or change the last two settings as you see fit.

The settings you pick here will be applied directly to the game's rendering engine. Set the aspect ratio to 4:3, otherwise the image will be stretched. There is no way to run the game in proper widescreen at this time. Because of this, it doesn't really matter whether you choose 1920x1080 or 1440x1080 as your resolution. Vsync should be enabled so that the framerate doesn't needlessly exceed the value you specified.

To force the game to use its Glide renderer:
1. Go to the Rogue Squadron folder (Default is C:\GOG Games\Star Wars - Rogue Squadron 3D\ROGUE)
2. Right-click on ROGUE.EXE and select "Create Shortcut"
3. Right-click on ROGUE.EXE - Shortcut and select Properties
4. Add "-voodoo3" at the end of the Target field, outside the quotation marks, then click OK. It should look something like: 5. Run the new shortcut, click on "Hardware Configuration", then "Change 3D Video Card";
6. From the drop-down box, select "Voodoo Card (Driver: GLIDE)", then click Accept>OK>Done>Exit to Windows

Done! Start the game like you would normally and it should now use nGlide and run in your desired resolution. You should see a 3dfx animation before the game logos, if you enabled it in the nGlide configuration tool.

Making a portable nGlide installation

You do not need to fully install nGlide to get it working:
1. Download the setup file from above and extract it using 7-zip or a similar program;
2. Copy the files 3DfxSpl2.dll, glide2x.dll, and nglide_config.exe to your ROGUE folder. You may delete the other extracted files.
3. Copy glide2x.dll to your Windows\System32 or Windows\SysWOW64 folder (for 32 and 64 bit versions of Windows, respectively).
4. Follow all the instructions on setting up nGlide, as above. Once you're done with step 6, you may delete glide2x.dll from your system folder (it was only needed there, so that ROGUE.EXE could detect it).

Windowed Mode through D3DWindower

To get this working, you will need to download D3DWindower and unpack it to your Rogue Squadron folder (Default is C:\GOG Games\Star Wars - Rogue Squadron 3D\ROGUE\). There are several possible mirrors to use:
Japanese Original:
http://www.geocities.jp/menopem/D3DWindower.lzh MD5: 9da511a067880f7410a866ee07f9aa3f

English Translations:
Version 1 MD5: b5eff19dfc41728936598008f436cd73
Version 2 MD5: 3a1de7771f274cc54c5196b022c64d68 - This is the version I've been using; it works identically to the Japanese one.

1. Open D3DWindower.exe. Here's a quick overview of what the toolbar buttons do:

First two buttons: Activate/Deactivate Emulation. They don't appear to work, at least not under Windows 8. We need not bother with them;
Middle two buttons: Add/Remove Program. They add and and remove programs from the list below;
Last three buttons: Run Program, Program Options, Open Folder. Again, fairly obvious;

2. Open the Rogue Squadron folder (as above), then click and drag "Rogue Squadron.EXE" to the D3DWindower list (Alternatively, click on Add Program, then browse to it);

3. Select Rogue Squadron on the list, and click the Program Options button. Set these up as shown in fig.1. The FPS counter is optional, while Cursor clip is only really necessary if you want to fly with the mouse;

4. Click the Run Program button. Rogue Squadron should start without issue, in a window.

NOTE: If Rogue Squadron has Admin privileges, you will need to give the same to D3DWindower. Otherwise, it will not be able to start the game. I have found no reason to give the game admin rights, or any compatibility settings, for that matter.

Using this method now allows you to ALT-TAB at will! As we've set it up, the game will pause whenever you do so. You may also instruct the game to continue running in the background, by ticking "Use Foreground Control" in the Foreground Control tab.

The game will start in a small window, as the logos and menu are only 640x480. The window will change size every time the in-game resolution changes; to avoid this, open the Program Options, as above, and set Width and Height to the ones you've set in the in-game options. In this, you are still limited by the game's choice of resolutions, unless...

Combining nGlide and D3DWindower

The two programs work surprisingly well together. Simply set up nGlide as described above, picking a window-sized resolution. You can even pick a 4K resolution to downsample from, but you need to set an explicit regular-window resolution in D3DWindower, as described just above. That aside, no changes need to be made in the D3DWindower configuration. In the Window Mode tab, you may now disable both GDI and DirectX 1-7 (DDraw), because the game will route all its graphical calls through Glide, which nGlide translates to D3D9. You will notice how the window no longer resizes: its rendering resolution is governed by nGlide and therefore uniform.

Widescreen (Experimental)

Thanks to CrazySteve88 for contributing his research on the matter!

See post 14 below for details.

Bugs and Humbugs

The game can exhibit some instability, particularly at the end of missions, with both of these programs. These crashes are infrequent and irregular. I do not consider them bothersome at all.

When you combine nGlide with D3DWindower, you may notice some spectacular washing out in the 2D menus. I am uncertain what causes this, but it is mostly tolerable. Using either program by itself causes none of these issues, so you may use that regime to do your menu setup. Additionally, hovering the mouse over buttons clears things up, so the menus are still quite usable.

There is a persistent in-game bug, often encountered with the Glide renderer, where the camera zooms extremely far away from the player craft, making flying very difficult. Hitting the brakes on the craft or resetting the camera (default is F1) usually restores the game to normal. An alternative solution is to switch entirely to cockpit view (default if F8). This bug is very old and not likely to be resolved immediately.

Setting up Controllers and Flight Sticks - HELP WANTED

I have neither controller nor flightstick on hand, so am sadly unable to test any configurations of these, or how they may interact with the two programs above. If you have done some tests like these (as thorough as possible, so more people can find them helpful), please share them here, so that I may include them.

When I use D3DWindower it just opens the launcher for the game and tells me to reinstall using the original disk

You must have pointed it to ROGUE.EXE. You need to use Rogue Squadron.EXE.

Also, please edit your post to remove the wall of text. One is enough, I think ;)

sorry, I didn't notice it added the quote.

no, I pointed it at Rogue Squadron.EXE

I did figure out if I add a hyphen in between Rouge and Squadron (Rouge-Squadron.EXE) it works

Now I can't get nGlide to work, I configured it exactly how you wrote it down, but it just skips straight to Dx6 with out even trying to load nGlide

Did you get step 6 to properly detect Driver: GLIDE? Is the resolution and refresh rate you've chosen compatible with your monitor? Are there any compatibility settings applied to Rogue Squadron.EXE? Those might interfere.

yes, yes and no

Can you try that hyphen thing and rename Rogue Squadron.EXE. I have known games that behaved differently depending on the name of their exe.

Sorry, I'm guessing blindly right now and your symptoms are really weirding me out :P

Just to make sure, you are pointing it at Rogue Squadron.EXE and not Rouge Squadron.EXE. It seems to be a very common typing error. Firstly, I read that Ctrl+J disables the joystick, so this may be a possible cause for users who don't get any joystick/controller in-game. Similarly, Ctrl+M is supposed to do the same for the mouse.

For me, when I use my 360 controller (wired) to play, it is actually going through vJoy, a virtual controller. Universal Joystick Remapper is what I am using to map my 360 controller to the vJoy controller functions. vJoy is set up as my primary controller, the 360 as secondary (done using the Windows Control Panel Advanced button to set the preferred controller). By doing it this way I get to apply a deadzone and sensitivity settings on the thumbsticks as the 360 controller software has no deadzone setting so old games often suffer from drift.

Actually, I just decided to test D3DWindower too (to see if I can fix the mouse lag) and I get the exact same thing. Rogue Squadron.EXE is the selected program but running it brings up the launcher instead and trying to play from there gives the reinstall from CD error message. :O

I tried that to, still nothing. I always end up with the strange crap happening on my computers.

Okay, making a copy of the executable (Rogue-Squadron.EXE) and using that in D3DWindower does get the game running. The mouse is still the same though. However, the turn left and right are now rolling the craft left and right, so the game is now unplayable.

Which of the three versions are you using? Try renaming the file and adding it again, maybe the program doesn't handle spacing too well.

To make the launcher work, I think you need the following registry entries:

Executable=.\Rogue Squadron.exe - can be relative or explicit
Install Path=C:\GOG Games\Star Wars - Rogue Squadron 3D\ROGUE - must be explicit

Or I might have actually hex-edited my own launcher and forgotten about it XD
I'll need to be off for a bit, but will get back later.

D3DWindower-rED, the one you said you were using.

Widescreen (Experimental)

Thanks to CrazySteve88 for contributing his research on the matter!

It is possible to hex-edit Rogue Sqadron.EXE to properly display widescreen resolutions in-game. However, increasing the field of view will reveal parts of the terrain before the textures for them have loaded. Remember: this was a game designed for the N64 and memory had to be conserved at every stage.

Widescreen is possible with both D3D and Glide, and the results are identical. Effecting the change involves modifying the resolution width and height, plus the aspect ratio (field of view). However, since nGlide allows for easy selection of resolutions, we only need to change the aspect ratio in order to get proper widescreen.

To use widescreen with D3D, follow this guide:
https://www.gog.com/forum/star_wars_rogue_squadron_3d/custom_resolutions_and_aspect_ratio_fix
You will still need to manually hex-edit the aspect ratio in order to get a non-stretched picture. See nGlide instructions 2-4 below.

To use widescreen with nGlide:
1. Make a copy of Rogue Squadron.EXE, call it Rogue16x9, Rogue1080p or however you see fit. We'll use RS_Widescreen.exe.
2. Open RS_Widescreen.exe with a Hex editor. You can use , [url=http://mh-nexus.de/en/hxd/]HxD, or even Notepad++ with the HEX-Editor plugin.
3. Go to offset 0016E042. It should have the value AB AA AA 3F.
4. Change the above value to 3B 8E E3 3F for 16:9 or CD CC CC 3F for 16:10; save the file.
5. Open nGlide_config.exe and pick your desired resolution; for Aspect Ratio, select "Fit to screen (Default)".
6. Run the game through RS_Widescreen.exe. To use this in combination with D3DWindower, you'll need to give the latter admin privileges and maybe force your desired window resolution from the first tab.

Again, remember that there will be missing terrain textures in the periphery. This has no effect on Taloraan or the Death Star, but is quite visible on other maps. Additionally, the HUD will be misaligned and stretched. The stretching should be fixable by editing the game's resource files, but remains work in progress. Aligning the HUD will require more Hex editing, as will rendering in widescreen the menus. These are also works in progress. Of note, no misalignment is present in cockpit view. Additionally, you may turn overlays off from the in-game settings, for a more "cinematic" experience ;)

NOTE: The aspect ratio fix above affects every 3D screen in the game: intro, hangar, briefing room, in-game. However, most of these have their resolution set independently, so you'll need to hex-edit some extra offsets to get them displayed nicely in D3D. nGlide, once again, circumvents this by rendering everything in your desired resolution.

i followed the instructions down to the letter for nglide, still cant get it to work. when i try to launch, it says reinstall from cd. ive tried everything.

i get no glide logo either. just doesn't seem to work.