|
|
Works for me. Please post a screenshot. This bug is another candidate for speedy closure. |
|
2006-09-28 14:32
|
pharos_bug.JPG (75,593 bytes) |
|
|
Here you go |
|
|
Try the same thing in a non-nebula mission. |
|
2006-09-28 16:03
|
pharos_normal.JPG (69,045 bytes) |
|
|
Everything is ok without nebula |
|
|
I'm betting that this is a data bug. Try without any extra VPs and see if it still happens. If not then we need to just close this. |
|
|
Don't bet, taylor, you lose. Checked without MediaVP. Screenshot is attached |
|
2006-10-19 16:58
|
pharos_bug_novp.JPG (66,699 bytes) |
|
|
You know, thesource2, you could be a lot more helpful and a lot less rude. It's really irritating to deal with you. You could have told us what build the bug first appears in, whether it appears in both the stable and unstable builds, whether it appears in debug or release builds, whether mediaVPs trigger it, all of that -- and you didn't. And now you're being rude to taylor. Cut it out. I've determined that it appears in the unstable branch only; it works properly in 3.6.9. It appears in both debug and release, with and without the mediaVPs. It seems to be related to the no-collide feature, as when I gave the Pharos the "cargo" flag it appeared normally. |
|
|
"Don't bet, taylor, you lose." I'm sorry if it seems rude to you, I NEVER intented to insult any of you. In my country it is common phrase. I first thought it is rendring order problem or some older problem with nebula heavy intersect. Does rendering order depend on object flags? |
|
|
i take it that this isn't a problem anymore. |
|
|
I've played through that part several times in the last year and don't remember having this bug. |
- Anonymous
