4096x4096 Textures

[Colin S]

Alright folks, so my last scenery as you know was KBLI and it utilized four texture DDS tiles with a  resolution of 4096. Now I'm making PHNL and the EXACT SAME TEXTURE SIZES AND SPECIFICATIONS don't work. Here is the log.txt exert from the moment that it crashed, and it has a peculiar litt line in it.

 

Aviation/Cessna 172SP/Cessna_172SP.acf
0:01:42.040 I/FLT: Init p0 type:loc_tak apt:PHNL rwy:08L
0:01:42.040 I/SCN: DSF load time: 1097935 for file Global Scenery/X-Plane 10 Global Scenery/Earth nav data/+20-160/+20-158.dsf (5371 tris)
0:01:42.040 I/SCN: DSF load time: 2137770 for file Global Scenery/X-Plane 10 Global Scenery/Earth nav data/+20-160/+20-157.dsf (88613 tris)
0:01:42.040 I/SCN: DSF load time: 711709 for file Global Scenery/X-Plane 10 Global Scenery/Earth nav data/+20-160/+21-159.dsf (50676 tris)
0:01:42.040 I/SCN: DSF load time: 38833 for file Custom Scenery/PNWS - PHNL/Earth nav data/+20-160/+21-158.dsf (0 tris)
0:01:42.040 I/SCN: DSF load time: 1033617 for file Global Scenery/X-Plane 10 Global Scenery/Earth nav data/+20-160/+21-158.dsf (71543 tris)
0:01:42.040 I/SCN: DSF load time: 653970 for file Global Scenery/X-Plane 10 Global Scenery/Earth nav data/+20-160/+21-157.dsf (54767 tris)
0:01:42.040 E/SYS: THREAD FATAL ASSERT: Trying to create a texture either less than 1 or greater than 2048!
0:01:42.040 E/SYS: THREAD FATAL ASSERT: Custom Scenery/PNWS - PHNL/IMG_1008.png
0:01:42.040 E/SYS: THREAD FATAL ASSERT: value:
0:01:42.040 E/SYS: THREAD FATAL ASSERT: 5632
0:01:42.040 E/SYS: THREAD FATAL ASSERT: /Volumes/RAID/code/design_clean/HLutils/TEX/TEX_obj.cpp:53
--=={This application has crashed!}==--

 

What was X-Plane 10 smoking at the time. If it were X-Plane 9 it would make perfect sense, but this is X-Plane 10. AND I've done scenery just like this before. AND I already tested one lone DDS tile to make sure they displayed properly in X-Plane 10. AND 5 together. AND I've done scenery in the past that had 100 orthophotos (but ended up violating some terms of use somewhere so it has long since been deleted) so I HIGHLY doubt that it has anything to do with the number of orthos I have (which totals around 19 at the moment).

 

Any suggestions?

 

ALL HELP WILL BE LOVED AND CHERISHED.

 

EDIT: And I'm not cutting up 74 orthophotos into 296 just to make X-Plane happy, it might as well be X-Plane 9 then.
 

Edited January 9, 2013 by Colin S

[Colin S]

ISSUE RESOLVED

 

Please don't laugh, this is serious stuff.

Upon closer inspection of the scenery file, it seems that somehow one of the photos from my summer camping trip became married to a *.pol file. This photograph was 18 megapixels. I would truly love to know how this happened. Honestly, I'd love to.

[chris k]

Ok, we won't laugh.

Yeah. It happens. Think we've all done this.

Always good to go back to the fundamentals. Check the .pol definitions. Check the images are actually the dimensions you think they are. Etc..etc.... Easy to miss something when theres lots of elements in the DSF.

[Colin S]

Ok, we won't laugh.

Yeah. It happens. Think we've all done this.

Always good to go back to the fundamentals. Check the .pol definitions. Check the images are actually the dimensions you think they are. Etc..etc.... Easy to miss something when theres lots of elements in the DSF.

 

 

Like I said, I got a massive picture of my pal Fred in a kayak at the lake rather than satellite imagery of Honolulu. Thanks though, I'll keep it in mind

[chris k]

I'd love to see a screenshot from WED. That'd be hilarious.

[Colin S]

I'd love to see a screenshot from WED. That'd be hilarious.

 

I'll actually take some time from PHNL to create a stupid scenery just for you, Chris. I need a break from schoolwork and PHNL. comedy will help a lot. Fred, here you come!