On Saturday 07 February 2009 11:50:57 FGD ML wrote: > 2009/2/7 Roy Vegard Ovesen <[email protected]> > > > On Saturday 07 February 2009 10:22:09 Roy Vegard Ovesen wrote: > > > As I said the .lwo file that Blender generated did _not_ contain any > > > reference to the texture image, so I don't think that putting the image > > > > in > > > > > the same path as the .lwo file will work. This could of course be > > > because I'm not using Blender correctly, but I think that is > > > irrelevant. We want > > > > to > > > > > test .lwo files created by LightWave, not .lwo files created by > > > Blender. > > > > Turns out I _did_ use Blender incorrectly. > > Well there you go! > > > I managed to create a Borgbox textured with a .png image from the FG data > > dir, > > and display it correctly in osgviewer. I would really like to repeat the > > test > > with a .lwo file created with the reference software LightWave. I don't > > see using Blender to create .lwo files as a realistic workflow > > We seem to be agreed there. It's OK for some I guess, I just have a > different taste when it comes to getting work done. I tend to like to be > able to see more of the job in hand, and far, far less of the interface. > > Can I take it you can now see the filename(s) in the .lwo? It's normally > down towards the end of the file.
Yes, full pathname to the .png image file. There is actually a bug in the exporter code that cuts one character from the path string (/home/... becomes /hme/...). I also tried to remove the pull path leaving only the filename, and copied the image file into the same directory as the .lwo file, but that did not work. > Go grab a copy! At least know how it /can/ be done. I always do that where > the maker makes it possible without fuss or gotchas of any kind. I see it > as meeting them halfway. It then has it's one chance to impress me, just > like anything else gets. Do you mean grab a copy of LightWave? -- Roy Vegard Ovesen ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
