The People's Mod

Phoenix-D · #1 March 6th, 2005, 04:05 PM

"I have spent some time looking through the code, and I believe I have found the problem. In Main_BitmapEffects.txt, Torpedo 13, had a speed of 1.2. While it is not documented, I believe that this value must be between 0 and 1, therefore, a value of 1.2 would result in a range check error."

I've used greater than speed 1 torpedos with no problem. The only issue is when you get to high speeds (>2), the torpedo has a tendancy to randomly explode.

Gandalf_greypilgrim · #2 March 6th, 2005, 04:06 PM

Okay, well, there goes that idea.

Captain Kwok · #3 March 6th, 2005, 04:56 PM

Yeah, I picked up a couple of range check errors in different systems after making the change.

Exan · #4 March 7th, 2005, 04:11 AM

In some versions I also noticed that sometimes when I turned the ship to face an asteroid field the game would give Range Check Error. Especially in the infamous Geneva system.

I try looking into this.

mottlee · #5 March 7th, 2005, 03:36 PM

On the sensors (int/ext) what is the diff as you go up in Lvls? I did not notice a diff in the discription between 1 and 2

Exan · #6 March 7th, 2005, 04:36 PM

I really can't say about that. The sensors weren't my doing. I guess the internal sensors shouldn't get levels at all since they only enable the ship status view. Or whatever that's called where you can view the components of your ship.

I can't recall what the ext sensors did.

Combat Wombat · #7 March 7th, 2005, 06:04 PM

I have gotten a bunch in Freeport