I’ve imported a large png file (1000x5176) that Unity only recognizes as being 197x1024. Since the width-to-height ratio is the same, and the height is that nice round 1024, I would guess that Unity enforces maximum dimensions. Is that the case?
You enforce it by your quality settings and the import size settings.
51xx though won’t work on 80% of the hardware as thats 8192 texturesize wise … 4096x4096 is commonly the maximum on many and already that is a 100mb+ block.
I would seriously recommend to split your image into realistically sized subtextures (rules of thumb: textures shouldn’t be larger than they can be seen on screen so at max the screen resolution)
Though recent cards will go up to 8192, Unity won’t currently go higher than 4096. Note that many older cards are limited to 2048; being able to import more in Unity doesn’t mean the hardware supports it.
Sorry, I probably should have specified that the image isn’t going onto an object as a texture; it’s just being displayed as a flat picture.
I guess it sounds weird to want to import and display a flat image larger than the screen, but the image is actually 4 pages of a manual that I want to scroll through (since a UnityGUI window will just chop off any part of an image that’s outside the bounds of the rectangle, all I have to do to make it scroll up or down is adjust the y value of the Rect for the GUI.Label containing the image).
I can increase the maximum texture size (in the Inspector, under Texture Importer), but this doesn’t help because I’m using the image a scripted UnityGUI object, and also because the image gets shrunk in the assets folder before I even insert it into the scene. Are there another set of import settings somewhere that control how Unity imports files into the editor?
100% of all images in Unity are textures on objects, including textures in the GUI. Everything is textures mapped onto polygons; that’s how 3D works. Again, a lot of cards are limited to 2048 max, so depending on how widely you want this to be used, you should break the texture up into 2048 pixel chunks.
Thanks for pointing that out - I didn’t realize (although it seems obvious now that the GUI objects were also polygons. We’re gonna cut up the image all the way to chunks of 1024 and then stitch them together when we scroll (and I’ll be sure to post that code in the scripts section when I’m done).