Lee Elliott writes: > On Wednesday 02 July 2003 11:32, Melchior FRANZ wrote: > > * Innis Cunningham -- Wednesday 02 July 2003 11:21: > > > Thanks Melchior I have found the area and modified the text will do a > > > build and see how it goes. > > > > Ahh ... don't bother. I've now dos-ified my a320-fb.ac and > > can reproduce the error. No, my patch does still not cure the > > problem, but I'm working on it. Thanks for helping to fix this. > > > > m. > > I saw this model come through when I did a cvs update a day or so ago but when > I loaded it in AC3D to have a quick look, it appeared to be untextered (and > unsmoothed). I had a look at the model and saw that the texture file was > mapped to the objects but when I looked at the texture in the AC3D UV texture > co-ordinate editor it just appeared to be a plain white rectangle.
Here is a screenshot of what I am getting with ac3d : http://perso.wanadoo.fr/frbouvi/flightsim/a320-ac3d.png As you can see, the model is textured but unsmoothed. The smoothing is made by the ac3d loader of PLIB. > I stripped out the texture info (Set all untextured) and saved the model with > a different name then reloaded it and confirmed that there were now no > textures assigned. When I tried loading and re-applying the texture, all I > got in the texture editor was the white rectangle again (I'd had a look at > the texture in the Gimp to make sure there was something there). > > I'd thought that there was a problem using non-square (^2) textures anyway so > I tried applying one from another model, that I knew worked, and I was able > to map it ok. > > I didn't get any errors when loading the model into AC3D but it definitely > doesn't like that texture. I have no problem to see the texture with ac3d v3.0 > It's a bit of an awkward one to get around too - although the texture is 1024 > x 512, it can't just be split into two 512 x 512 textures because the > fuselage areas are longer than 512 and the wind-screen also runs across the > boundary. > > Both of these areas of the texture could be stretched (or compressed, rather), > so that they fit in 512, but that would reduce the quality. The fuselage > could be split into two sections (front and rear) to match the fuselage > areas, if they were split, but the windscreen would still have to be scaled > (there's not a lot of detail in them so there wouldn't be too much quality > loss). > > I don't know if this could be causing the error msg - I guess it's possible > though. The problem was line endings -Fred _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
