thx Joshua. There are plenty messages that certainly could use bits of finetuning (read: total rewrite) as well, so please feel free send me corrections.
Fabrice On Jan 9, 2011, at 1:35 AM, Joshua Granick wrote: > Haha, yeah. > > Not only is grace important for non-native English speakers, this is all free > software :) > > > I might write it like this: > > > Warning: The loaded model "MyModel.dae" contains invalid or defective > geometry or UV data. > > Some of this data has been repaired, but other data (such as proper UV > mapping) is probably ruined. You should consider using a different export > format or correcting this file using a 3D model editor. > > 20 out of 42 UV definitions were invalid. Default UV's have been applied to > avoid a possible application crash. > > > > On Sat, 08 Jan 2011 15:41:20 -0800, Fabrice3D <[email protected]> wrote: > >> first: Prefab is dev and maintained by an old french guy: So funcky english >> is tolerated! >> I'll update the message with "not valid" as I do not think "invalid" is >> correct either no? >> >> Now the message translation: >> of 42 uv's objects tested, Prefab found 20 where either : >> 1/ no uv definition was found, Prefab would then generate new ones, if there >> are no neighbour faces found on 3 sides of the "not valid" face >> that the app could use the restore the missing uv data, default values u/v >> 0/1, 0/.5, 1/0 are set. >> In most cases, especially with Sketchup, no uv's were found and default is >> applied. >> 2/ you have uv's out of range either higher than 1 or lower than 0. Often >> found from generators where repeat is standard in buildin uv editors or map >> projectors. >> 3/ uv's are defined but values are NaN's. Some exporters are either having >> errors or totally mess up uvs, such as .3ds or .ase exports from AC3D for >> instance. >> >> That's why it looks weird once loaded. Because the mapping you have defined >> is totally wrong. >> >>> would it be best to avoid SketchUp and simply use Prefab for all 3D editing >>> functions >> There is no modeling feature yet in Prefab. Which would be indeed very handy >> for this kind of cases and beyond... >> Pitty you cannot see yet what runs on my screen atm ;) >> >> When it comes to uv edits, sure Prefab's editor should do the trick. >> >> Fabrice >> >> On Jan 8, 2011, at 10:26 PM, Brian Bosak wrote: >> >>> ?Hi. I am trying to load a DAE file from SketchUp and am getting UV errors >>> when attempting to open the file in Prefab. If I load it directly through >>> Away3D using one of the loader classes, it simply fails with an exception. >>> In Prefab, the following message appears: >>> "The model loaded holds defect or unvalid information (why isn't it >>> invalid?) in its geometry definition. Some of the data was repaired but >>> uvmapping being probably ruined you should correct this model in a 3D >>> editor..." >>> "20 invalid UV definition was found during the parsing of 42 UV's objects. >>> Default uv's were applied to avoid possible crashes in this application" >>> The model did show up with incorrect UV mapping, making my brick building >>> look really strange, and it doesn't appear that BSP mapping works correctly >>> either.... >>> If I create 3D models in Blender, those load OK, but models from SketchUp >>> don't seem to load correctly. Even extremely simple models such as basic >>> blocks. With this many problems (no offense intended to any developers; I >>> know how hard it must be to make such a wonderful 3D engine. Other 3D >>> engines for Flash, and even desktop 3D engines such as XNA have similar >>> problems. Away3D seems to support a lot more formats than other engines); >>> would it be best to avoid SketchUp and simply use Prefab for all 3D editing >>> functions? >> > > > -- > Using Opera's revolutionary email client: http://www.opera.com/mail/
