Project Excaliber (XBR) Video

[Jeff Mottle]

As some of you know, Autodesk hosted presentations on January 27th outlining some of the details of Project Excalibur (XBR) XBR encompasses many of the technologies and changes that Autodesk may implement in 3ds Max in coming releases. I recorded today's presentation (with Autodesk's permission) and have posted it here:

 

http://www.cgarchitect.com/news/AUTODESK-EXCALIBUR-XBR-3DSMAX-PREVIEW.shtml

 

Please use this thread to provide feedback or discussions.

[kenpimentel]

Here's a blog posting some stats and a link to the captured session:

http://area.autodesk.com/blogs/ken/excalibur_xbr_revealed

[Ricardo Eloy]

I attended yesterday's presentation. Gotta say I was impressed. All of the things discussed were really important (to me, at least) and the feeling that the whole 3ds max crew is paying attention to what we do and need out here was there through the entire presentation.

I'm very optimistic about the future of 3ds max. It's shaping up to be really great.

Congrats to Shane, Ken and Pierre-Felix for this initiative.

Cheers

Rick Eloy

[wrt]

Thanks Jeff, I really appreciate the capture and posting. I wasn't available for the meeting so I was excited to be able to watch later.

 

b

[kenpimentel]

If you want statistics and the "official" capture, look here:

http://area.autodesk.com/blogs/ken/excalibur_xbr_revealed

[raterry]

I attended th 8PM and am thankful for them keeping us involved. not to mention very optimistic and excited about the direction they are taking.

[wrt]

Ken thanks for the link. I'm extremely excited about XBR. Among the many amazing features planned, documents and node-based render pass management etc. sound like a dream to me personally. Seems like some of the younger folks familiar with node-based algorithmic modeling in Grasshopper will be familiar with that way of working even if they come at design visualization straight from architecture these days. I'm familiar with it from programming, engineering design, and Maya but seems like some of the younger folks would be able to jump right in.

 

Thanks again for the presentation and the hard work on the platform.

 

b

[kenpimentel]

Great to hear! Of course, talk is cheap. We now have set expectations and we need to deliver on some of them. Hope you don't have to wait long.

[Justin Hunt]

Thank you, it does excite me alot, now you just need to pull it off:)

 

jhv

[Dave Buchhofer]

Product advancements notwithstanding, this newfangled 'Communicating' phase at Autodesk is very welcome after the past decade.

 

I managed to catch about half of the video, It looks promising, aggressive, and huge, and i have to say, i wish you guys the best of luck with the backwards compatibility beast.

[Brian Smith]

I enjoyed the presentation but it still would have been nice to have a public viewing of at least one new feature in action for the next release of Max. Certainly one feature wouldn't be a matter of national security or compromise the future of Autodesk.

[Jeff Mottle]

I believe the SEC rules prevent them from doing that. If I recall correctly any prior announcements of new products/features force them start reporting revenue differently which could cost them millions. Maybe Ken can clarify exactly how that works.

[Brian Smith]

I believe the SEC rules prevent them from doing that. If I recall correctly any prior announcements of new products/features force them start reporting revenue differently which could cost them millions. Maybe Ken can clarify exactly how that works.

 

You may be right...don't know. Would be curious to know. Hearing that at the start of the video would probably do wonders to quell any frustration. Took 10 mins to get through the 'rules' of the presentation so maybe a 15 sec mention of the SEC rules would be in order.

 

At the very least, can't they 'accidentally' leak something and blame it on someone else

[kenpimentel]

I posted a blog that explained it all in detail a few months ago. I think it was called "all secrets revealed" or something.

 

Any feature or release disclosure by us before announcement is extremely painful to the company. Not a good career move. I think we are trying to disclose what we can when we can. Sorry it isn't enough!

[quizzy]

At the very least, can't they 'accidentally' leak something and blame it on someone else

 

it wasn't me!!

[Justin Hunt]

Its something that you have covered many times and in detail, some understand the reasons and there are others who will always push for more.

 

What will be interesting is to see the affect these developments will have on existing users and new users.

 

For me personally node based workflows scare me. Mainly because of lack of experience using them and when I have they seem fiddly. Powerful - yes, huge shift in working practice - definitely and ultimately the best way to do things, I'll wait and see:)

 

jhv