Re: [Vrmlengine-main] 3ds conversion problem?
Game engine supporting many 3D/2D formats and graphic effects
Brought to you by:
kambi
From: Michalis K. <mic...@gm...> - 2009-01-20 02:37:49
|
da...@la... wrote: > On Tue, 20 Jan 2009, Michalis Kamburelis wrote: > >> da...@la... wrote: >>> as I'm working with view3dscene I am finding that some of the doorways do >>> not fully penetrate the walls. can you tell if there is an error in the >>> 3ds file or if it's in the conversion? >>> >> All I know about 3ds is basically what my engine can display... How >> *should* it look like, i.e. what do you mean by doorways not penetrating >> walls? Which format in http://vrml.lang.hm/vrml/ is the source file? >> >> I compared kadota-land.3ds and kadota.3ds viewed by view3dscene with >> what is shown after importing these 3ds into blender, resulting geometry >> is pretty identical, so on the 1st look I see no errors in view3dscene >> 3ds handling. > > around the 'back' of the house there are two sets of stairs. there is a > door at the top of each of the stiars, but that door doesn't go all the > way through the wall. for one door you can see it from the outside, but > not the inside, for the other you can see it from the inside, but not the > outside. > Ah I see them (the ones on the attached screenshot?). Blender importer shows the same geometry for them, with the same problem --- so it looks like this is what is stored is 3ds file. > hmm, I'll consider it, but that would trip me up when I work on the model > with other tools and external objects. That's why the "Inline" trick could be helpful, as then your 3ds data stays separate from VRML things. Oh, and I of course forgot to attach the sample VRML file that shows this inline --- attaching now. Michalis |