|
|
Post by thyme on Jun 20, 2004 12:19:46 GMT
www4.tpg.com.au/users/gilldawn/seamless3d/seamless2News/seamless3d.zipThis version of seamless3d 2.044 is now ready replacing 2.043 as the official version of Seamless3d It has a number of nasty crashing bugs removed that existed in 44e including the fatal feature spotted by halibut and the zero intolerance that existed in the BranchJoin's vertexLen spotted by bumpy and a bug I found that caused seamless to crash way to easily when build nodes were deleted in a certain order. I know of some bugs in 2.044 but it should be reasonably robust and more stable that 2.043 even withstanding the fact that 2.044 has undergone some major surgery since 2.043 in regard to the morphing nodes. The changes were done before I have documented these nodes. I will document them soon I hope with some step by step examples showing how to make an avatar using BranchJoin nodes and building a mouth that utilises the Morpher node for animation. The two examples buildTextureAv.smls and buildColorPerVertexAv.smls files from my seamlessWayExamples.zip and seamlessShowcase.zip files have been updated for the new morphing nodes. I have updated the files for registering seamless II nodes in VrmlPad Seamless 2.044 supports the generation of X3D HanimDisplacer nodes when H-Anim is selected for output (the standard nodes for morphing single skin mesh avatars) and can even display a generated HAnimDisplacer node in action with some limitations. For all the bugs found reported since 2.043 many thanks to Miranda, Bumpy, Marboro, Halibut, Florenze, Barph and Ep and everyone else's time for bearing with my user unfriendly bugs. best wishes thyme
|
|
Barphe
New Member
:p
Posts: 30
|
Post by Barphe on Jun 20, 2004 14:03:32 GMT
Hi Thyme,
I noticed the other day that the export shape funtion does not actually write any geometry.
I had messed up and compiled a transformation that I didnt like, and I had other GOOD changes I hadn't saved. So I opened a previous version, exported the same part to a file, then opened the working version and deleted the part, made a new part, then tried to import the geometry from that exported file.
Nothing happened. I opened that file and there is everything there execpt a shape. hehe
|
|
|
|
Post by thyme on Jun 21, 2004 4:39:47 GMT
Sorry Everyone I just found out the two examples buildTextureAv.smls and buildColorPerVertexAv.smls from the seamlessWayExamples.zip and seamlessShowcase.zip files that I updated last night for the new Morpher nodes had a hidden bug in them that could randomly cause a crash. These two files have now been fixed and uploaded. Glad the fault did not get traced back to 2.044 in the end because it looked for a while like it was one of those most nasty bugs a bug that happens randomly the type that can take any amount of time to isolate. I was trying to debug seamless for quite some hours but turned out I was barking up the wrong tree  Please delete the old example files if you have downloaded them and replace with the new to save your self from a super frustrating episode of confusion. kind regards thyme |
|
bumpy
New Member
Posts: 8
|
Post by bumpy on Jun 21, 2004 6:03:47 GMT
Hi thyme and seamless friends ;D What do you think about starting a subject thread for reporting bugs in seamless? That way you (thyme) can do bug tracking (yuk! I sound like my software quality manager  ) and we (seamless friends) can report new ones or see if there are known work arounds etc.. umm... does sound like a lot of work though  All the best, bumpy  |
|
|
|
Post by thyme on Jun 21, 2004 10:26:52 GMT
Hi Thyme, I noticed the other day that the export shape funtion does not actually write any geometry. I had messed up and compiled a transformation that I didnt like, and I had other GOOD changes I hadn't saved. So I opened a previous version, exported the same part to a file, then opened the working version and deleted the part, made a new part, then tried to import the geometry from that exported file. Nothing happened. I opened that file and there is everything there execpt a shape. hehe thanks barf for bringing this to my attention. I looked into the export part function and found it worked ok for ColorEffect but I had not written the code for exporting textured triangles yet. 2.045 now has this missing code added. www4.tpg.com.au/users/gperrett/seamless3d/index.htmlI tested exporting the arm of textured avatar as a standard shape node and importing it back all seemed to work ok. all the best thyme PS I put the link to my seamless page because I thought there is a extra bit of security this way after thinking it is to easy perhaps for someone to post a link here to a exe file containing malicious content |
|
|
|
Post by thyme on Jun 21, 2004 10:52:45 GMT
Hi thyme and seamless friends ;D What do you think about starting a subject thread for reporting bugs in seamless? That way you (thyme) can do bug tracking (yuk! I sound like my software quality manager ) and we (seamless friends) can report new ones or see if there are known work arounds etc.. umm... does sound like a lot of work though All the best, bumpy Hi Bumpy I have thought about this before but writing about bugs is a full time occupation I try to get rid of a bug where possible before spending the time to write about them in any detail and how to work around them since I am so slow at writing instructions I find it is often faster for me to take the more direct route of elimination However some bugs do have to be lived with for a while so will think about it some more. best wishes thyme |
|
bumpy
New Member
Posts: 8
|
Post by bumpy on Jun 22, 2004 8:33:47 GMT
Hi thyme Yes I can't help but agree, writing about bugs is a waste of life. Some months i write more about them than i do code  ... I guess here (a new seamless version post) is as good as anywhere to report bugs etc... or should i just send you an email? I have been working on my seamless tree and it's comming along quite nicely thankyou ;D. But i have had a bit of trouble with the pos/neg z branch joins. I can't get them to (always) work like the x axis joins do. No real problem though coz i just use the BranchJoinNegX and rotate it around to the z axis. That always works when Ive got everything right. Also when I try to join a major branch, which has minor branches, to the trunk, the the minor branches get left behind. I can fix this by adding another Place node with the same rotations and translations as the join but this gets a bit tiresome. Is there a better way? Just ran seamless 2.045 on my giga fast work PC, same problems with the z joins, but man it sure runs smoooOOoth ;D Take care, bumpy |
|
|
|
Post by thyme on Jun 22, 2004 21:19:49 GMT
Hi Bumpy Until I get more bugs than I can keep up with please send any findings of bugs here as it is more motivating for me this way heheh. Please send the file where pos/neg z branch joins failed. Essentially these functions should work the same as x functions internally so hopefully I should soon be able to fix them. Perhaps because I never use these much is why they have some bugs left in them I don't know about. Thanks much for you support ;D thyme |
|
bumpy
New Member
Posts: 8
|
Post by bumpy on Jun 23, 2004 1:23:20 GMT
Hi thyme OK  it seems to be working properly now! I must have been doing something wrong before or maybe it only happens after some bizzar sequence of operations . Anyway if i get it happen again i will let you know. bye for now, bumpy |
|
|
|
Post by thyme on Jun 23, 2004 19:44:50 GMT
Hi thyme OK it seems to be working properly now! I must have been doing something wrong before or maybe it only happens after some bizzar sequence of operations . Looks like the code I added to seamless to make the user think they are going mad is working just fine ;D Oooops I was not meant to post this here! thyme |
|
) and we (seamless friends) can report new ones or see if there are known work arounds etc.. umm... does sound like a lot of work though 
... I guess here (a new seamless version post) is as good as anywhere to report bugs etc... or should i just send you an email?
it seems to be working properly now! I must have been doing something wrong before or maybe it only happens after some bizzar sequence of operations