CompuServe Thread

#When is 3.0?

7 messages in this thread
#76767From: Brad BlockMar 12, 1994 10:58 PM
Hi! I am anxiously awaiting release 3.0 and all its fabled features. I haven't been around lately and don't now when the latest release date is. Can anyone at Impulse (Mike) help me out? Thanks, Brad Block
#76782From: Stan Kalisher (Impulse)Mar 13, 1994 7:50 AM
Brad, We are done with the code and are just doing the final touches on the manual. It looks like two or three weeks, and then it will no longer be a fable it will be a reality. We are using 3.0 here at the office and we all have big smiles on our faces. Mike
#76788From: Peter GreciMar 13, 1994 10:42 AM
Cool Beans!!!! So Barring any mishaps 2.9 owners will be 3.0 recievers by April 1 or so. Yabba Dabba Doo and all that rot. Sounds GREAT. Did all the features that are metnioned in the printout shipped with 2.9 make it into 3.0? You know the list on page 3 thats as follows….. Bones Kinematics Improved Anti Aliasing New Light Sources with improved shadows Shadow Mapping New Stage and Animation Tools Thanx for the info
#76821From: Stan Kalisher (Impulse)Mar 13, 1994 6:36 PM
Peter, Yep they all made it and more. Mike
#76892From: Peter GreciMar 14, 1994 4:03 PM
Woca Woca "they all made it and MORE" !!!!!! Thanx for the info Mike. My Brain Froths in anticipation.
#76933From: David HoganMar 14, 1994 9:58 PM
How about DXF?
#77121From: Charles BlaquiereMar 17, 1994 7:37 PM
Mike, Since we're talking 3.0, can you tell me whether any of the following will be implemented? Thanks! – All filename fields have a button that pops up a file requester. Currently, if you want to edit an existing Actor filename, or the Globals reflection map, etc… you have to remember the long path+filename and enter it manually. – Stage editor will support all 3 pick methods: click, drag box, lasso. – Detail editor's status bar will show current state; if several states look the same in wireframe, you can easily pick the wrong state to update. – Replicating an object won't lose sharp/soft edge status. – No more seam where altitude map edges meet, when using WrapX and/or WrapZ, or when using "repeat" in FlatX/FlatZ. Blaq!