Textures look really nice Wolf. Sorry, the creasing on the payload bay doors looks so horrible. The mesh got messed up some how.
I think you need the new updated mesh that’s currently only available through the SSU SVN repository. As you probably can tell by going through this thread, alot of texture mapping issues were found and fixed which makes these textures look bad with the run of the mill SSU 4.2 mesh.
The mesh I m using is AFAIK the latest available. Have you released a new update in the last week?
Fixed that: https://www.dropbox.com/s/otr6f3czsyyvb81/Atlantis_on_pad.jpg?dl=0I think Donamy referring to this:
View attachment 15661
Am I right?
BTW my textures have been changed a lot to fit the latest mesh uploaded via SVN. If anyone is using any previous mesh they will show a lot of mis-matchings in many areas
I was referring to the creases in the doors. They should be smooth.
Don't forget about the OMS pods! The OMS pod textures can be changed by adding LOMSPodTexture= and ROMSPodTexture= to the appropriate mission file.
Just do what I wrote in the previous post. These two lines control what textures are used for the OMS pods for that particular mission. The SSU mission files are just regular ASCII text files and can be edited by any text editor.I thought there was no way to have dedicated OMS pods for Columbia (and Challenger). How can I add them?
Name=STS-1
Orbiter=Columbia
OrbiterTexture=Columbia_original
LOMSPodTexture=PORT_OMSpod_STS1
ROMSPodTexture=STBD_OMSpod_STS1
ET=SWT
ETFRL=TRUE
SRM=SRM
LaunchSite=KSC
LaunchPad=LC-39A
MLP=1
TargetInc=40.300000
TargetLAN=0.000000
MECOAlt=116676.000000
MECOVel=7824.216000
MECOFPA=0.296000
PerformRollToHeadsUp=FALSE
OMSAssistEnable=FALSE
OMSAssistDuration=59.000000
MaxSSMEThrust=100
UseRMS=FALSE
UseKUBand=FALSE
UseSTBDMPM=FALSE
UseODS=FALSE
UseExtAL=FALSE
UseTAA=FALSE
AftTAA=FALSE
HasBulkheadFloodlights=TRUE
HasDragChute=FALSE
Bridgerails=8
PayloadZPos9=8
SILTS=FALSE
LogSSMEData=TRUE
UseCISS=FALSE
CISS_GPrime=TRUE
UseASE_IUS=FALSE
ASE_IUS_AftLocation=FALSE
InternalPRSDTankSets=2
HasEDOKit=FALSE
EDOPallets=0
Just do what I wrote in the previous post. These two lines control what textures are used for the OMS pods for that particular mission. The SSU mission files are just regular ASCII text files and can be edited by any text editor.
So the STS-1 mission file would look something like this:
Code:Name=STS-1 Orbiter=Columbia OrbiterTexture=Columbia_original LOMSPodTexture=PORT_OMSpod_STS1 ROMSPodTexture=STBD_OMSpod_STS1 ET=SWT ETFRL=TRUE SRM=SRM LaunchSite=KSC LaunchPad=LC-39A MLP=1 TargetInc=40.300000 TargetLAN=0.000000 MECOAlt=116676.000000 MECOVel=7824.216000 MECOFPA=0.296000 PerformRollToHeadsUp=FALSE OMSAssistEnable=FALSE OMSAssistDuration=59.000000 MaxSSMEThrust=100 UseRMS=FALSE UseKUBand=FALSE UseSTBDMPM=FALSE UseODS=FALSE UseExtAL=FALSE UseTAA=FALSE AftTAA=FALSE HasBulkheadFloodlights=TRUE HasDragChute=FALSE Bridgerails=8 PayloadZPos9=8 SILTS=FALSE LogSSMEData=TRUE UseCISS=FALSE CISS_GPrime=TRUE UseASE_IUS=FALSE ASE_IUS_AftLocation=FALSE InternalPRSDTankSets=2 HasEDOKit=FALSE EDOPallets=0
Shouldn't be a problem if you include the modified mission files.That means I have to add the related textures since they do not exist in the SSU/textures folder..
IMHO. The printing on the white tiles, should be smaller and lighter. It also looks like it is indented on the tiles, where in fact it is just printed on the surface. Nice job though.
There is: Just don't apply normal mapping to the labels, just the tile gaps. See what I did with the OMS pods.I am afraid there is no solution other than not using normal maps.