Hi everyone!

As a background, I've played and loved this game since it game out. I remember having dual SLI 3dfx VooDoo cards, and thinking this was the best looking game out there! And it still looks good to me.

I went ahead and purchased the game from GOG, because I hope it helps GOG keep bringing classics back to the PC, and also because I couldn't ever get my Independence War to install or work on anything since XP. :)

I am running Windows 8.1 64-bit on a Razer Blade 14 (2014 w/Touch Screen Version).

It took me hours to figure it out, but I am using my Wireless XBox Controller repammed through UJR.

So with all that out the way, here's my problem:

My PBC shots do not register damage about 90% of the time (It sseems to increase the longer the mission goes and the more you fire.)

Note: PBCs do damage anywhere under 10kms, but their optimal damage range is under 4kms. I am aware of this and it is not the issue.

- I hear the damage 'sound effect' explosion.
- I have tried rapid fire, and single fire.
- I have tried dual and single forward facing PBCs.

I've actually pinned my fire button, put the ship into 'Approacch', and listened for 20 minutes as explosions indicate my PBCs have hit the target, for only the enemy ship to get up to about 19% damage, then slowly repair itself.

I've also noticed that when you Rapid fire (or continually fire a single PBC),, it seems to 'Overheat' after two successive shots. Which I do *NOT* remember happening in the original game unless severe damage was sustained.

----------------------------------

So here's where it gets interesting:

If I run IWar.exe direct.... The PBC functions fine, and all 'explosive' hits cause damage. Huzzzah! Result! But the graphics are obviously in Non-3Dfx mode (which I am fine with, I like the 'retro feel'). *HOWEVER*, the game will crash any time you enter Capsule Drive through a LaGrange point (I assumed it was switching to cut scene, but I have a feeling it's actually crashing on the animation of the external view of your Corvette as it disappears into the LeGrane point.)

Way to notice:
If you run with the Glide Driver (Other than the 3Dfx logo), your in game mouse cursor will be a Circle with a Crosshair through it.

If you run the game without the Glide Driver (IWar.exe ithout the -b -16, for example), your in game mouse cursor will be a '+' (Simple crosshair).

When you get the '+', your PBCs will work..

SoooOooOOoOOoOOooOOoo...

Running iWar.exe direct:
+ Plays the game in non-glide mode.
+ Undamaged ship will rapid-fire single PBC Indefinitely
+ No PBC Overheat
+ PBC hits record damage correctly.
+ Awesome retro look and feel.
*BUT*
- Game Crashes at LeGrange point entry.

Running iwar_start.exe
+ Plays the game in Glide mode.
+ Game is stable, does not crash
- PBC Overheats in two shots.
- PBC hits do *NOT* register correctly
- Game is practically unwinnable

I have tried:
Modifying Glide Settings
Trying iWar.exe options (-b -16, -hidef, -1024x768, etc)
It comes down to running in Glide or not.
MSI Afterbburner
nVidia Application options for IWar.exe
Running IWar in Compatibility mode
Trying alternative VooDoo drivers

The only two times I have come close to having i work right:
Using RIVA via MSI Afterburner to Lock the IWar.exe FrameRate to 60 (But the MSI Afterburner showed it was playing at 40).
- After rebooting it never worked again.
- Not sure if it was a fluke, or coincidence, but I shutdown Independence War 3 times and tried, and all times the PBC did damage with every hit under 4kms.

Updated Glide to v.13, and created an nVidia profile for IWar.exe, and it seemed to work as well, but when I reset the profile settings, I could never get the PBCs to hit accurately.


----------------------

My Question(s):

I am making the assumption that iwar_start.exe *MAY* fix my cutscene problem, but runs the game in 'Glide' mode.
Is there a way to run iwar_start.exe so that it kicks off IWar.exe in 'Non-Glide' mode?

or

Is there a way to do whatever worked in my 'fluke' attempts with RIVA and nVidia profile, but do it via iwar_start.exe.

Im assuming that it's the 'Framerate' problem that's been mentioned in several other posts (as that's the only thing the RIVA settings seemed to influence with the IWar.exe app).

----------------------

Apologies for the long read, but I wanted to be detailed in case anyone else is having this problem, and hopefully these details will lead to a solution, or at least save people some of the efforts I've been through.

I am grateful for the original game, it is a classic, and the GOG team for bringing this game back!

Thanks,

Vic...

Some threads that might hold relevance:

http://www.gog.com/forum/independence_war_series/weapons_not_causing_damage

http://www.gog.com/forum/independence_war_series/weapon_hits_not_causing_damage

http://www.gog.com/forum/independence_war_series/double_front_pbc_not_doing_damage

Thanks mucho for the response and help!

I've been through those, it's what led me to try to the MSI Afterburner / RIVA framelock, the nGlide Drivers set (Frame Rate setting), and then trying to limit the framerate via the nVidia tool.

As an odd thing, another topic said 'Setting Star Blur: On' in the game setting kills your frame rate.

It does kill your frame rate, however it also fixes the PBC hitting problem.

So yes, I agree, it seems that slowing down the game is the solution.

I'm going to mess with RIVA again to see if i can use it to lock down the framerate. I had it working once before, but deleted the profile and never got it to work after that.

Thanks for the replies!

Vic...

I am running the original CD version. My mouse cursor is not any type of cross at all. It is more or less a regular cursor shape, except yellow like the rest of the interface. My executable is called "EdgeOfChaos.exe". Am I running with or without Glide?

Also, what is PBC?

PBC = Particle Beam Cannon.

Standard PBC's have an effective range of 5km or less (approx), Quad PBC's have even less range. Also PBC blasts lose energy quickly, so the closer you are the more damage they do.

Edge of Chaos is I-War 2 is Direct3d so no Glide, CapnSnuggie is refering to I-War 1.
I-War 1 has a bug that when the framerate exceeds 120fps or so it doesn't register hits anymore, can be solved easily by turning on v-sync or set a refresh rate of half of it like 60Hz or so depending on your display.

Doh!