It's coming along, the only hold ups on it is the OMS pod texture and that I don't have any photos or images of the PLBD structure under the two deployable radiator panels. Then it is updating the various individual orbiter textures.How is the new mesh coming along? I think that's the main thing that's still holding up the release.
How is the new mesh coming along? I think that's the main thing that's still holding up the release.
I don't see any reason to hold up the release it for the new meshes/textures, but I'll leave it up to you to make that decision, as I'm fine either way.Do we really want to include the new meshes in the release? Or can we release without them?
I'll check it(#14).I'm fine with releasing without the new meshes.
Looking at the open tickets, I think we can do Tickets #26, #27 and #32. I think Ticket #20 is already fixed. DaveS, do you have time to look at Ticket #14? I think this is only a texture issue now, and the code is working.
The orange texture for STS-1/2 is to simulate the unpainted SWTs used on STS-3/4/5/7. Doesn't the lines BURNT_TEX and ET_TEX_NAME work?I thought I had checked the fixed code in, but I hadn't. The burnt ET code should be working now, but the burnt texture needs to be fixed to work with the newest meshes.
---------- Post added at 11:53 PM ---------- Previous post was at 11:44 PM ----------
One other thing I noticed about the ET textures is that the STS-1 scenario has an orange tank instead of the correct white tank. Also, if we do use the white tank colour at launch, it will become brown at SRB sep when the burnt texture is used. I can add either a scenario line or a config file setting to indicate the name of the burnt texture to be used. I think the config file setting is better.
Question: Should I go ahead and add the deployment mechanisms for the forward radiator panels? Or is that unnecessary detail?
The ET_TEX_NAME line should work, but it's not used in the STS-1 launch scenario. The BURNT_TEX line just indicates that the burnt ET texture is being used, and doesn't specify the file to use.The orange texture for STS-1/2 is to simulate the unpainted SWTs used on STS-3/4/5/7. Doesn't the lines BURNT_TEX and ET_TEX_NAME work?
Could the BURNT_TEX line be converted to take a file name instead? That would solve our problems with the SWT.The ET_TEX_NAME line should work, but it's not used in the STS-1 launch scenario. The BURNT_TEX line just indicates that the burnt ET texture is being used, and doesn't specify the file to use.
I meant the differences in the tanks themselves.
I don't see any problems with this. What is your reason for not wanting this or better yet, being so against the implementation of it?So you need a way to set up each tank with the correct flight. God forbid you fly the wrong ET with a certain mission. Really ?