[Nx]

This here says 2048x2048 textures are unnecessarily large.

The Aeolus has a 1024x1024 texture in mv_assets, and a 2048x2048 texture in mv_adv

The Iceni has a 2048x2048 texture in both, and the ship is certainly larger, but I'm not sure if a 1024x1024 texture wouldn't be sufficient there.

I tried using a single 2048x2048 texture for a destroyer, and the level of detail is not adequate. So, what should I do? I'm thinking of splitting it into 2 maps, so that I can have either two 2048 textures for highend machines (the mv_adv equivalent) and two 1024 textures normally.

By not adequate, I mean that while it looks detailed enough in the tech lab, when you fly really close with your fighter, the individual panels are often larger than your fighter - and I can't add more detail because the texture lacks resolution.

[The E]

2048^2 maps are not that unreasonable anymore.

However, as someone for whom that is the max texture size supported by my GPU, I'd recommend providing one of those in addition to a 4096^2 map for the people who can use it.

At any rate, 4096^2 is probably the best compromise between quality and memory usage.

[Galemp]

You can really use any size texture you want, so long as both dimensions are powers of two. So, I'd recommend using a 4092x2048 texture instead of two 2048 textures. Keep in mind, though, that most video cards won't like textures over 2048.

You have to draw the line somewhere, though; try using your textures more efficiently. If your model is symmetrical, you only need to UV map one side and mirror it. See if you can reuse UV space; take a close look at the high-poly Karnak, to see how you can get the detail of a tile-mapped texture on an unwrapped model.

I also assume you're familiar with the use of glow maps, shine maps, and most importantly normal maps. These can lend a lot of detail to your textures.

[Nx]

I'd like to avoid using textures over 2048 for compatibility reasons. The problem is that I don't feel the 2048^2 texture is adequate for "normal" quality either. Then again it may be that I just suck at texturing.  

The model is symmetrical, but the uv map is not fully symmetrical to fix seams that appear when a flat surface is normal mapped and has a texture seam (see this thread)

The Karnak suggestion is interesting, but I don't think I can reuse enough to make a difference.

Anyway, here are some screenshots to illustrate what I mean (click to see bigger version):





The black circle with the grey circle in the middle that you see on this next image is 12x12 pixels on the texture - just an illustration of the relative size of the texture:



And the docking point, which is significantly less detailed than the FS2 dock tile:



Edit: Actually, the dock tile is 128x128 pixels, while this is approx. 85x85 pixels - so it's not that bad..

[Spoon]

This here says 2048x2048 textures are unnecessarily large.

That was written in 2005 

[Galemp]

That doesn't look too bad, actually...

[Scooby_Doo]

What? 4096 is the new 2048? oh great LOL

[starwolf1991]

No, Never! 4096 is not the new 2048.