USS Enterprise Texture Problem

Tips for creating and manipulating planet textures for Celestia.
Topic author
cljohnston108
Posts: 17
Joined: 06.07.2005
Age: 57
With us: 14 years 8 months
Location: Los Angeles, CA
Contact:

USS Enterprise Texture Problem

Post #1by cljohnston108 » 23.10.2013, 16:55

I installed fungun's "Star Trek at Home" add-on (all 3 volumes), but got this weird thing happening with the saucer texture on the Enterprise in the DryDock...

Image

I've consulted with Tim Wilson via Facebook, but he wasn't able to reproduce the problem.

I'm running Celestia 1.6.1 on a 6-year-old iMac running OS 10.5.8

Any help would be greatly appreciated!

Avatar
John Van Vliet
Posts: 2723
Joined: 28.08.2002
With us: 17 years 7 months

Re: USS Enterprise Texture Problem

Post #2by John Van Vliet » 24.10.2013, 08:08

i would have to download them and check

though i am not running a mac , i am running on linux

this is the older 1.6.1 and not the pre 1.7 ? right ?


to me it looks like the UV mapping is off

is this the ONLY mesh that is a bit messed up ?
or are there also others ?

i should know something in about 24 Hours

Avatar
John Van Vliet
Posts: 2723
Joined: 28.08.2002
With us: 17 years 7 months

Re: USS Enterprise Texture Problem

Post #3by John Van Vliet » 25.10.2013, 02:54

Most of this is bitching at the add on Creator
"fungun" DOSE KNOW BETTER !!!!

your fix will be at the end of my rant


the 9 errors about "DefSat" named custom orbits
1)" Could not find custom orbit named 'DefSat' "
2)" Could not find custom orbit named 'DefSat' "
3)" Could not find custom orbit named 'DefSat' "
4)" Could not find custom orbit named 'DefSat' "
5)" Could not find custom orbit named 'DefSat' "
6)" Could not find custom orbit named 'DefSat' "
7)" Could not find custom orbit named 'DefSat' "
8)" Could not find custom orbit named 'DefSat' "
9)" Could not find custom orbit named 'DefSat' "

( you can not define these in a ssc file, this is NOT how it works )
and if there are more than 5 of these warnings this CAUSES code failures in celestia

the two errors for "dry dock 2"
and the two errors for the USS Enterprise

" Could not find custom orbit named 'Dry Dock 2 0.500' "
" Could not find custom orbit named 'Dry Dock 2 0.500' "
" Could not find custom orbit named 'USS Enterprise 0.400' "
" Could not find custom orbit named 'USS Enterprise 0.400' "

the errors about
" Could not find custom orbit named 'Spacedock 7' "

the manny errors about the unnamed " " quoted blank space
Could not find custom orbit named ""
-- 6 of these
Could not find custom orbit named ""
Could not find custom orbit named ""
Could not find custom orbit named ""
Could not find custom orbit named ""
Could not find custom orbit named ""
Could not find custom orbit named ""



and in reading the ssc for the uss enterprise
i found a problem
the dry dock AND the ship are listed TWICE
one is set to
Visible true
and the other to
Visible false
this is causing the drydock AND the enterprise to be drawn by the graphics card TWICE
however one of then is INVISIBLE
but the 3d card is still creating TWO dry docks and TWO ships
occupying the EXACT same space at the exact same time

and that can cause graphics glitches



there is also a linux and Apple Mac ERRORS in or around Jupiter station
-- the uss volga NEEDS FIXING !!!

-- This is one of the REASONS i started checking add ons
to STOP THE MICROSOFT WINDOWS ONLY ADD ON'S !!!!!!!!!!!

Apple Mac's and Linux operating systems ARE CAPITALIZATION sensitive !!!


/texture/medres/CARPTGRY.* : unrecognized or unsupported image type
the damn file extension is IN ALL CAPS !!!!!!!!!!!!!!!!!!!!!!!!
CARPTGRY.JPG
this is add on class 101
NO CAPITAL FILE EXTENSIONS !!!!!!!!!!!!
that is a very big PROBLEM !!!!!!!!!!!!!!!
they are ALWAYS LOWERCASE !!!!!!!!!!!!!!!!!!!!


/texture/medres/PORTA.* : unrecognised or unsupported image type
/texture/medres/PAINEL03.* : unrecognised or unsupported image type
/texture/medres/PAINEL05.* : unrecognised or unsupported image type
Painel005.jpg --- This is a capitalasation ERROR
/texture/medres/CARPETE.* : unrecognised or unsupported image type
-- AND --
/texture/medres/ARM.* : unrecognised or unsupported image type
Arm.jpg -- This is a capitalasation ERROR
celestia is looking for a ALL cap named image and it it NOT IN ALL CAPS !!!!
the name of the image IS CORRECT "Arm.jpg" this is a correct capitalization
the name in the 3d mesh IS WRONG

------------ end of the rant ----------

As to your fixing of this mess
well the drydock and enterprise should be fairly easy
open the ssc file called "Drydock.ssc" in the folder "SolVol1v3b"


and edit it so it looks like this
by putting a # at the start of these lines
this is for the two that are invisible ( "Visible false" )

Code: Select all


#"Dry Dock2" "Sol/Earth"
#{
#   Mesh "newdrydock3.cmod"
#   Radius 0.500
#        Visible false

#   CustomOrbit "Dry Dock 2 0.500 "
#   EllipticalOrbit {
#      Period  0.064176392
#      SemiMajorAxis 9767
#      Eccentricity 0.1
#      Inclination 7.0049
#      AscendingNode 0.33167
#      LongOfPericenter 77.456
#      MeanLongitude 125
#   }

#   Obliquity  0.01
#        RotationPeriod 84
#   Albedo  1

#}

/*---- and this section also ------*/

#"USS Enterprise2" "Sol/Earth"
#{
#   Mesh "1701on.cmod"
#   Radius 0.400
#        Visible false

#   CustomOrbit "USS Enterprise 0.400 "
#   EllipticalOrbit {
#      Period  0.064176392
#      SemiMajorAxis 9767
#      Eccentricity 0.1
#      Inclination 7.0049
#      AscendingNode 0.33167
#      LongOfPericenter 77.456
#      MeanLongitude 125
#   }

##        Orientation [90 0 1 0]
#   Obliquity  0.01
#        RotationPeriod 84
#   Albedo  1

#}



then you need to put a # infront of TWO other lines in this one file

the line "CustomOrbit "USS Enterprise 0.400 "" that DOSE NOT have a # needs one
and the line " CustomOrbit "Dry Dock 2 0.500 " " that dose not have a # needs one places in front of it


then on to the image issues in the cmods
these cmods are ASCII text so they are easy to edit
-- very time consuming but easy
check the image name in the medres folder with the name in the 3d mesh file ( the .cmod file)

and change the namr in the cmod OR in the medres folder so that they MATCH

this should have been done by fungun BEFORE he uploaded it to the motherlode

fungun
Posts: 315
Joined: 30.07.2007
Age: 58
With us: 12 years 8 months
Location: Iowa, USA

Re: USS Enterprise Texture Problem

Post #4by fungun » 25.10.2013, 03:27

1. It was checked, passed, and loaded to the Motherload.
2. It was long ago, probably before anyone check them for Linux, Mac users. Therefore I was never made aware of errors.
3. There are 2 Drydocks and 2 Enterprises because of the use of the switch.celx script included in the addon.

So it can be marked as Windows only or removed. It is up to you.

Tim

Topic author
cljohnston108
Posts: 17
Joined: 06.07.2005
Age: 57
With us: 14 years 8 months
Location: Los Angeles, CA
Contact:

Re: USS Enterprise Texture Problem

Post #5by cljohnston108 » 25.10.2013, 08:15

Thanks for the help, John!

Okay, so I edited the ssc as you instructed, but as for the cmod, I really don't know what I'm looking at, since I know nothing about coding or texturing.
I looked through the 347 texture files, but since the problem is limited to the Enterprise saucer section...

Image

...I only checked these against the cmod:

botsaucspec
botsaucx
botsaucxioffx
enterpriseidglow
enterpriseidglowi
enterpriseidglowioffx
topsaucspec
topsaucx
topsaucxioffx

They all seemed to match up, but then, as I said, I don't really know what I'm looking at.
I only know hashtags block out lines of code, and I see a lot of those in these material sections...

Code: Select all

# DscUp has 1 material(s)

material # 168

# diffuse  1 1 1
#  diffuse weight 0.7     # Kd
  diffuse 0.7 0.7 0.7
  opacity 1
  texture0      "topsaucx.*"

# specular  0.737 0.737 0.737
#  specular weight 0.3     # Ks
  specular 0.221 0.221 0.221
  specpower 81     # (roughness)*2.55
  specularmap      "topsaucspec.*"

#  emissive  0 0 0
#  emissive weight 0.8     # Ke
  emissive 0 0 0 # product
  emissivemap      "topsaucxioffx.*"
 

end_material


Is it supposed to look like that?

Avatar
John Van Vliet
Posts: 2723
Joined: 28.08.2002
With us: 17 years 7 months

Re: USS Enterprise Texture Problem

Post #6by John Van Vliet » 25.10.2013, 22:16

the only other thing i can suggest is re-download the SolVol1v3.zip
it might have gotten a bit corrupted in transit .


Return to “Textures”

Who is online