[redmenace]

alright, seems theres something else specific I need to do to the project files/

[jr2]

Page 1 has links to the latest builds, but try going to http://fs2source.warpcore.org/exes/latest/ and opening the folder named after the month you're looking for.

[Trivial Psychic]

Try it out with any build from January 16th through February 22nd.  These don't give the error messages for me, but I haven't tried them in-game, because they're incompatible with TBP.

[IPAndrews]

There's an issue with player-use-ai and player-not-use-ai, when used in conjunction with ship-change-class. The issue being when the ship comes back under player control the player is not allowed to fire secondaries. The secondaries are actually there and you can still choose single or dual fire, but it's as if the selected secondary is non-existent (off the bottom of the list). I can provide missions to demonstrate if anyone wants to have a look. I can't Mantis it either because I use a hotmail account. 

[CaptJosh]

I could send you a gmail invite, man. I think Mantis allows gmail accounts.

[Starman01]

Oh, and in addition to my posted mantis bug #0852, I can partially reproduce it now (since it happens everytime again when I rebuild that mission).
Unlike my other missions, this is the first time I use transports with docked container,  so maybe there is something wrong with the docking-code, but that's just for information what I did different in this mission.

However, I figured out two situations where these white textblocks appear.

1) I place so many highpoly ships that I ran out of system-memory
2) I place a model in a large distance away from the mission-area center, in my example + 50.000 units on the z-axis.

Now, I really fear to ask, but have you people changed/reduced the size of the mission-area ? I sincerly hope not 

Sorry for being impatient, but could a coder please help me with that one ? I am now able to reproduce the error partially. When I move the object far away the white box error appear, when I move it back the info is displayed again. Though I'm really afraid to destroy my other missions, since the crash error stays even when I delete everything except Alpha1.

My big problem now is, that there seems to be no backwards compatibility. I used this FRED version to save my old missions, and now they don't work with the old FRED again. On the other hand, the new exes crashes some of my missions. I'm not sure why, but at the special crash point I use the "change IFF" and "ships visible" SEXP, did you change anything here ?

Also the distant stuff would be vital, do you have made any changes here ? WCS needs real big mission areas to use the autopilot system.

Any help would be appreciated. I'm stuck now, I can't go back to the old one, and can't move further with the new one

[Shadow0000]

Also the distant stuff would be vital, do you have made any changes here ? WCS needs real big mission areas to use the autopilot system.

You mean the limit of about +700,000 meters that is created from Alpha 1 Initial point, where your ship is destroyed by being consider that you abort the area mission ? (that would be helpful for anyone, actually I have the impression that my ship is inside a sphere, not so FreeSpace after all)

[starfox]

Try Star Wars Rougue Squadron III, and you will understand what it means to fly in "enclosed area".
HECK, I seriously hate that "feature", it's so damn annoying when you finally get the feeling of the fierce dogfight with skilled friend...the "automatic turnaround system" ruins it all !!!

Anyway, about the distant limit, it also could be used to warn the player about entering 3D-planet's "atmosphere", IE being too close to planet/sun...I think the same warning system was used in Freelancer.

[Starman01]

Not sure if it is/was 700.000 meters, I rather think something about a cube with a side length of 150.000 meters. However, for a good autopilot-simulation I make the navpoints at least 50.000 klicks apart from each other, rather more if only fast fighters acompany you. Still, the newer fredbuilds act really strange now

[Shadow0000]

Try Star Wars Rougue Squadron III, and you will understand what it means to fly in "enclosed area".
HECK, I seriously hate that "feature", it's so damn annoying when you finally get the feeling of the fierce dogfight with skilled friend...the "automatic turnaround system" ruins it all !!!

In the Stars Wars - Shadow of Empire for N64 it's like that, yes it's a know "feature" of SW games.....

Anyway, about the distant limit, it also could be used to warn the player about entering 3D-planet's "atmosphere", IE being too close to planet/sun...I think the same warning system was used in Freelancer.

I am replacing and adding 3D Planets and Spherical Moons to Sol: A History, but there are some non-spherical models exceptions which I can support (Deimos and Phobos). That would just be a Flag in FRED if distance less than then you calculate the distance from the planet where the gravity field start, so there is no need for such an imposed limit.

Not sure if it is/was 700.000 meters, I rather think something about a cube with a side length of 150.000 meters. However, for a good autopilot-simulation I make the navpoints at least 50.000 klicks apart from each other, rather more if only fast fighters acompany you. Still, the newer fredbuilds act really strange now

It's much more than that in the SCP, I have created a Moon model at real scale about 3500 KM or so in size, and it could travel even to distances of 400,000,000 or so with no limits, and the collision data was totally OK.

It's some limitation bothering in the code, it doesn't make sense why even all the other 99 Ships can be a year light from you, and you can't even move 700,000 from your initial point, after 700,000 or so the 3 Warnings start and then you blow.

[Triple Ace]

Something is wrong with Redmenaces builds. No matter which one it is my system always locks up. Goobers builds work just fine though. Any ideas why? I would like to use some of the newer builds.

[Paladin1]

Something is wrong with Redmenaces builds. No matter which one it is my system always locks up. Goobers builds work just fine though. Any ideas why? I would like to use some of the newer builds.

I have also encountered lock-ups using the latest CVS builds specifically the 3/06/2006 build by Redmenace in the the main FS2 mission Endgame, i've just switched back to Goober's 20060212 build and I can now proceed past the mission.

[neoterran]

I've also experienced lockups with the latest builds. The 3.6.7 official and the 3.6.7 media vps plus patches are the only combinations that allow me to play Freespace with the full effects, as well, otherwise, i'm missing the engine glows on many ships. This is a real pain if I want to run the updated Inferno....

*edit* Well, I figured out some things about the 3.6.8 Mediavps that gave me my engine thrusters back, but I'm still having trouble with the lockups. From what I can tell they happen with all builds in march that i've tried so far (3/1, 3/4, and 3/6). I'm currently using 2/28 build, i can't go back much farther or Inferno and the 3.6.8 mvp config I have won't work.

[DuncanF]

Yeah i'm getting random lock ups in the more recent CVS builds as well, at random times as well, never consistant.

[CaptJosh]

Have to report similar behavior, at least under Windows. Haven't tried refreshing my CVS and doing a new build in linux recently.

[Cobra]

can i make a complaint? why the hell does the P4 optimized builds run slower than the plain ones?

[Cobra]

It's called Real Life.

[neoterran]

Well, before it gets rebuilt, someone should take a serious look at why the recent builds are freezing up like that and the 3.6.7 release isn't. There's not much point in releasing new builds if they're causing random freezes on many systems. 

[Cobra]

Bah, wasn't thinking when I posted.

[karajorma]

Well, before it gets rebuilt, someone should take a serious look at why the recent builds are freezing up like that and the 3.6.7 release isn't. There's not much point in releasing new builds if they're causing random freezes on many systems. 

How about running the debug build using the window option from Dev Tools in the launcher. Then you can tell us what's causing the lock up

The last few lines of the debug spew should help.