Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: Kosh on November 13, 2003, 01:01:46 am
-
This applies to both retail FS2 and FS open
After getting that access violation during the FS1 port (on "A failure to coomunicate"), I decide to replay the FS2 main campaign in the retail version. Then I get to a certain point (I forgot which mission) and it gives me an access violation. I also found another user made campaign out there, everything works great except that at a certain point during the first mission, I get another freaking access violation.
Considering how many of these dang things I get, I feel that this needs to be brought up. In general, how can they be troubleshooted in both FS open and retail FS2?
-
mm.. good question
/me looks like a monkey doing a math problem
-
For the Port, were you using 2.2 or 2.1?
Later!
-
I was using 2.2. I know for a fact that I'm not the only one who has been having access violation issues. I think we need to start looking into this. Ignoring the problem will not make it go away.
-
nailing these things is like caching magots from an overturned garbage can, unpleasent and you'll get the majority of them quickly but there'll always be a few that find a nice dark crack to hide in and unless you look directly at that crack at just the right moment you won't find it, even then you'll probly have no way to get it out
-
I too had this problem with the Port mission you mentioned, under 2.2. It has something to do with the revised ship's table file for 2.2. If you disable the 2.2 vp (and remove the ships.tbl if you've happened to extract it from the vp) and it should work fine. Then, just reactivate 2.2 once you've completed the mission. As for the mission in FS2, can't help you with this one.
Later!
-
Originally posted by Bobboau
nailing these things is like caching magots from an overturned garbage can, unpleasent and you'll get the majority of them quickly but there'll always be a few that find a nice dark crack to hide in and unless you look directly at that crack at just the right moment you won't find it, even then you'll probly have no way to get it out
:wtf: :wtf: :lol:
we do enjoy pain
-
Originally posted by Bobboau
nailing these things is like caching magots from an overturned garbage can, unpleasent and you'll get the majority of them quickly but there'll always be a few that find a nice dark crack to hide in and unless you look directly at that crack at just the right moment you won't find it, even then you'll probly have no way to get it out
:lol: :lol: :lol:
Excellent analogy, Bobboau. :nod:
-
my biggest concern is that bob actully catches maggots from underneath an overturned garbage can :wtf:
-
If you disable the 2.2 vp (and remove the ships.tbl if you've happened to extract it from the vp) and it should work fine.
Thanks, it worked.
-
I work in a meat packing plant, every once in a while someone will leave something eadable in a trash can in the summer over the weekend, and when you come back it'll fall over and its a game of catch the maggot before the federal inspector walks by.
:)
-
yummy. its a shame too, i had teh munchies
-
nothing ruins the appetite like the sound a magot makes when you squish it
POths
-
fs2_open_r caused an Access Violation in module fs2_open_r.exe at 001b:00599510.
Exception handler called in Freespace 2 Main Thread.
Error occurred at 11/15/2003 14:11:08.
C:\FS2\fs2_open_r.exe, run by Plankersj.
1 processor(s), type 586.
383 MBytes physical memory.
Read from location 00000008 caused an access violation.
I got this when I was replaying the FS2 campaign under FS_Open. Everything works until I get to "Into The Maelstrom". It happened right at the end when the Collosuss shows up. This is exactly why I made this whole f****ing thread in the first place. This is really getting annoying. And then the fact that when these things are brought up (especially by me), they are practicly ignored. Also the fact that only 1/3 of the replies in this thread actually have anything at all to do with the topic is not helping to change that opinion at all.
-
except thats not going to tell us much. we're going to release a debug build so you can get better error handling.
-
is that the mission after kings gambit?
-
we're going to release a debug build so you can get better error handling
Thank you.
is that the mission after kings gambit?
It's after The Sixth Wonder.