[TrashMan]

So I set up a escort mission trough an asteroid field. Everything OK, I play the missinon when I notice my transports are getting pwned.
Why?
My wingmen are nowhere to be found. I look around only to find them 17000 meters away chasing an invisible, indestructable asteroid.

[Droid803]

I get invisible asteroids too..
except that they're not 17000 m away. They're the things which are pwning what I'm trying to escort. I see these white brackets which smack into a ship and explode...

[Capt_Thunder]

I get a few invisible asteroids as well. They haven't stopped me from finishing a mission.  But they are a nuisance. Could this be a glitch with the game, or compatibility with nvidia graphics cards? Do you set your graphics to use direct X or openGL. I remember getting invisible ships when I played a freespace port mission. But that was solved when I upgraded. It was odd. It was firing at me, but my gun and missiles were going straight through.

[TrashMan]

I get invisible asteroids too..
except that they're not 17000 m away. They're the things which are pwning what I'm trying to escort. I see these white brackets which smack into a ship and explode...

Oh, it's not 17000 meters away at the start.
But it passes nearby and my wingman with the guard order go chasing it as it slowly moves away.

Order them back is not an option since the player shouldn't have command authority over the fighters. I could probably use a complex SEXP that changes AI orders whenever they move too far back, but as soon as I give the guard order they will chase the next invisible asteroid anyway.

[TrashMan]

So this appeared before and by other too?

Is it in Mantis?

[blowfish]

I'm pretty sure this is a known issue with the mediavps that has been fixed in the internal gamma release...

[TrashMan]

Then they better hurry releasing the latest media VP's...

[Vasudan Admiral]

From the Common Issues thread in the support forum:

Invisible asteroids / Missing ship textures.

Enable jpg/tga textures from the Features list in the Launcher (only with fs2_open_3_6_9).
Use a 3.6.10 build.

[TrashMan]

Strangely enough, there is no such feature in the launcher.
Guess I'll have to add it in manualyl then.

[Wobble73]

Strangely enough, there is no such feature in the launcher.
Guess I'll have to add it in manualyl then.

If the feature isn't in the launcher it may be because you are already using a 3.6.10 build, in which that has been removed from the launcher as it is always switched on by default.

[TrashMan]

And yet the invisible asteroids are still there....

[Droid803]

-jpg/tga cannot be the case even though I'm using 3.6.9, as I am certain it was enabled.
On top of that, I had ships with TGA textures (namely blowfish's HTL Aurora), and they showed up fine.

[Mongoose]

I just had this happen earlier today when playing a nightly build from two weeks back or so with the 3.6.10 beta VPs.  In fact, it made the first mission of Procyon Insurgency nigh-unplayable, since my wingmen decided to gallivant around 15 kilometers away from the convoy that was getting hammered by asteroids.  The rest of the asteroids in the mission showed up fine.

[Vasudan Admiral]

People who are experiencing this please test older builds - because there's no media issue that could cause this in the betas as all asteroid maps are DDS.

So, if this is occuring with the beta MVP content, it's most likely a FSO issue that needs mantising.

[TrashMan]

I'm using s2_open_3_6_10r-20080926_r4832.exe and it's happening.

Just how much older builds should we try out?

[phreak]

Code: [Select]

Warning: Couldn't open texture 'asterod3'
referenced by model 'ast03.pof'

Warning: Couldn't open texture 'asterod3'
referenced by model 'astb03.pof'

These are probably known issues, but missing textures will cause collision errors for some reason.

[TrashMan]

I'll try extracting them, converting them into .pcx or something. Mayhaps that will work.

[Zacam]

That file does exist though. And it (on the source I tore apart from Beta) is not corrupt.

[Vasudan Admiral]

Err, are you sure about that? In my beta set I have ASTEROD1, 2, 5 and 9, while ast03.pof and astb03.pof do indeed reference ASTEROD3. As far as I can see, Phreak's correct.

(Note - the new asteroids use 1 2 and 5 only, so this was indirectly fixed internally ages ago now, which makes this an easy bugfix indeed. )

[Zacam]

Hmmm. You are right. I confused the fact that none of the asteroid POF's use 09 to assume that all were present with an equal.

Rename a copy of ASTROD9 into ASTEROD3?