project-navigation
Personal tools

Author Topic: missing textures in mission "base defend"  (Read 1201 times)

Offline Tlactar

  • Rookie
  • ***
  • Posts: 60
    • View Profile
missing textures in mission "base defend"
« on: September 15, 2009, 01:55:28 am »
my large hangar is missing some stairs (or their textures...) on the defend mission, also there are quite a lot of invisible objects blocking space, only visible as shadows on the 3rd. screenshot.

r26164

Win 7 x86 RC, Geforce 9600M GT, Core 2 Duo P8400, 4GB RAM (or 3.xGB <- 32-bit)
« Last Edit: September 15, 2009, 01:58:07 am by Tlactar »

Offline Destructavator

  • Combination Multiple Specialty Developer
  • Administrator
  • PHALANX Commander
  • *****
  • Posts: 1908
  • Creater of Scorchcrafter, knows the zarakites...
    • View Profile
Re: missing textures in mission "base defend"
« Reply #1 on: September 15, 2009, 02:00:52 am »
Hmmm...  I noticed this "phantom staircase" (only shadows) issue myself quite a ways back, I thought it was fixed since then - Looks like I'm wrong - Thanks for pointing it out!

Offline Tlactar

  • Rookie
  • ***
  • Posts: 60
    • View Profile
Re: missing textures in mission "base defend"
« Reply #2 on: September 15, 2009, 02:03:23 am »
if it depends on base layout (who knows? Well, probably you do, but... ah whatever ^^) here'd be a save right before the attack.

edit: And another thing on the base defend map - one of the entrances has stair on the outside - but they aren't passable (see screen)
« Last Edit: September 15, 2009, 02:32:15 am by Tlactar »

Offline Destructavator

  • Combination Multiple Specialty Developer
  • Administrator
  • PHALANX Commander
  • *****
  • Posts: 1908
  • Creater of Scorchcrafter, knows the zarakites...
    • View Profile
Re: missing textures in mission "base defend"
« Reply #3 on: September 15, 2009, 03:25:35 am »
Quote
edit: And another thing on the base defend map - one of the entrances has stair on the outside - but they aren't passable (see screen)

Yeah, I had that same problem in that exact map segment as well, and coincidentally I thought that bug was also fixed at some point.