I know Steve goes for the 'full-fat' experience as he has >4GB and 64bit Windows, so loads everything. I have seen the same issue once or twice with the same model when other programs were loaded in memory. It most likely failed to load the texture.
I've been extending the error checks when loading models and hopefully this won't happen in future. This area also seemed to be the main cause of start-up crashes so will see if that is improved in the next version.
v1.06 is still current as I ran out of time before Christmas to really test / expose cut-off distance values for drawing planets/asteroids. Flying into a busy asteroid field or near by a gas-giant with several of its asteroidal bodies/moons on screen would destroy frame rates. Doing some final testing and hopefully 1.07 will be out later today...
(the model is 74 for 4-arms, 77 for 2 arms and by default use large 2048x2048 textures. There are smaller versions within the skinpack folder of model 77)
I've been extending the error checks when loading models and hopefully this won't happen in future. This area also seemed to be the main cause of start-up crashes so will see if that is improved in the next version.
v1.06 is still current as I ran out of time before Christmas to really test / expose cut-off distance values for drawing planets/asteroids. Flying into a busy asteroid field or near by a gas-giant with several of its asteroidal bodies/moons on screen would destroy frame rates. Doing some final testing and hopefully 1.07 will be out later today...
(the model is 74 for 4-arms, 77 for 2 arms and by default use large 2048x2048 textures. There are smaller versions within the skinpack folder of model 77)
Last edited: