|
2006-01-17 16:37
|
asteroid-01.jpg (225,515 bytes) |
|
2006-01-17 16:38
|
asteroid-02.jpg (183,227 bytes) |
|
|
Does Lightning Marshal have its own set of asteroids? |
|
|
I don`t know. How can I check it? |
|
|
This is known problem and it remains since FreeSpace 1 (Descent FreeSpace). There is an object called Asteroid (not asteroid field but single asteroid). This object is transparent for anything but light, i.e. it is visible but ships and weapons can fly right through. I don't think it can be fixed and doubt it must be. |
|
|
Yea thats the "Asteroid" you can place on its own in FRED. You can fix it by removing the "no_collide" flag in its table. |
|
|
I don't think it's related to that. This sort of thing used to frequently happen in dense asteroid fields and was a known issue in retail FS2 (something to do with the "collision pairs" limit IIRC), but I haven't run into it in any FSO builds for quite a long time. Maybe the bug has somehow returned in the latest builds. edited on: 01-18-06 03:46 |
|
|
Ah, yes. In FreeSpace 1 this bug present too. If there are too many objects in the map some of them can become "transparent". It can happen with ships also not only with asteroids. |
|
|
Collision pairs are dynamically allocated now so that can't be the problem. I'll try and take a look at the mission later today. |
|
|
It's just the mission, not a code bug. Those low poly asteriods are ships, with no_collide set (as phreak said). |
|
|
Not-A-Bug. |
- Anonymous
