C4d 10.5<-->Vue6.5 XStream any tutorials?

[Chadman]

Hi Bill

I have only recently purchased Vue 6.5X stream for use with C4D and can't direct you to any tutorial thats are dedicated to Vue Xstream & C4D but l can give my experience thus far.

Killing of C4D files... yes this does still happen now & then, l have no idea what the cause is. All l can say is just make sure you have C4D doing auto backups.

The other issue that l wasn't aware off before l bought Vue was its Antialiasing problems when it comes to animations. You can get clean animations but you have to have the Object Anti Aliasing quality thershold at somewhere between 90% & 100%, at least this is what l've experienced.

Having said all that some of the enviroments you can make are pretty unreal... it's just a bummer when you frames render 8mins plus.

Chad P :)

[Bill-D]

<<Having said all that some of the enviroments you can make are pretty unreal... it's just a bummer when you frames render 8mins plus.>>Chadman


Thanks Chadman- really usefull the antialiasing tip and the auto save settings. BTW in your qoute above, I take it that "pretty unreal" in this context is meant as a plus?

cheers
Bill-D

[kvb]

Actually had a couple of files burned a couple weeks ago. Problem was clicking yes when asked if I'd like to save changes to the vue scene (within c4d after trying to save my c4d file). Just don't tweak your vue scene AT ALL in c4d until they fix that. Switch over to the vue interface and make changes/save there. Probobly a lot safer.

As far as antialiasing, I read somewhere that there was a setting in the render dialogue that was "meant" to fix that exact problem with animation. I think it was the texture antialiasing or something like that. Check cornucopia, as some people from e-on posted there how to eliminate (doubtful) or severly decrease the animation/artifact issues using that setting (you'll know you've got the right article when they start talking about 40% all the time).

Other than that... good luck:)

kvb

[Bill-D]

Thanks a lot KVB

Thats indeed a serious fault and I also need to animate the composite. I'll follow your advice. I have visited Cornucopia a couple of times to see the gallery, but didn't check out the forum, but now I will as its become more relevant.

BTW how's tech support at Eon? I sent an E mail query a week ago (as requested) but answer came there none.

Bill-D

[Chadman]

Bill the "pretty unreal" statement was a positive remark and as soon as you start playing with the sky settings you'll see what l mean.

Here is a link to a thread within the Vue Animation topic over at the Cornucopia forum. the title of the thread is called "All Out War On Flickering" you should be able to find some starting pionters there at the very least.
http://www.cornucopia3d.com/forum/viewtopic.php?t=5649

Just be careful with the "Texture Filtering Setting" within the Texture Anti Aliasing settings tab. I leave it on the crisp setting 0% as l've found it to change the colour of your textures using at anything above 0%.

Cheers

Chad P

[Bill-D]

Thanks again Chadman. Its a relief to Know that those awesome examples of what VUE can do which appear on various sites is not a myth. They remind me of the shock we all had at seeing the very first images and anims of Bryce 1 in the early-mid 90's.

I will be walking on eggshells as I progress to linking Vue to C4d, with hundreds of saved states and backups on very remote discs. Thanks also for the tip about the "texture Filtering
Setting".

The other compaint I read about on this forum last year was Matching the positions of the C4d and Vue cameras, do you know if this is still a problem?

Regards
Bill-D

[Chadman]

Well l'm still a bit new to working with C4D & Vue Xstream myself at this point in time, so l can't really confirm that issue at the moment. I bought Vue Xtream to assist me in completing a project for an Irrigation company so it's been a bit of a trial by fire.

At this point in time l'm thinking l will model all non enviroment objects within C4D and export them as OBJ format, then import them with Vue and texture and render them within Vue. The reason for this is that if l can keep all the rendering within Vue then l can use all the 5 network render cows that come with Vue, if l render within C4D then l only have one machine rendering as you can't use net render with VUE unless you buy a render node for each extra render machine.

The other option which l would prefer if l could work out a way to do it would be to get only the camera data from Vue some how into C4D, this way l could texture & render any C4D elements within C4D and then comp them in within AE, but l haven't worked out a way yet to get only Vue's camera data within C4D and if there is way then this might be where the 2 systems camera's not matching may rear it's head.

Chad P

[Bill-D]

<< At this point in time l'm thinking l will model all non enviroment objects within C4D and export them as OBJ format, then import them with Vue and texture and render them within Vue.>>

A good Plan Chadman. Can you use ordinary Jpeg/psd textures as in C4D?

<< The other option which l would prefer if l could work out a way to do it would be to get only the camera data from Vue some how into C4D, this way l could texture & render any C4D elements within C4D and then comp them in within AE >>

I hope this works, because trying to plan moves separately in the 2 packages would be a nightmare. Did you find the Vue learning curve reasonably easy after C4d?

Bill-D

[Chadman]

Bill l haven't used Jpeg's or PSD's etc. for texture side of things such as colour & so on. But what l have used textures for is for distribution of different textures with on a terrain. For example l wanted to have a sandy type texture for a dirt road next to a irrigation channel, so l done a very basic greyscale texture for a terrain channel cut away within the terrain itself but then this allowed me to use this texture in photoshop as a reference to do a greyscale jpeg that would be white where l wanted one texture and black where l wanted the other texture.

I learnt this from a tutorial at www.geekatplay.com and there are many other great tutorials there so l suggest you check it out.

As far as getting Vue's camera data into C4D without any terrain, ecosystems etc. the only way that l can think of at the moment is to save a duplicate of your project from VUE but delete everything bar your camera. Then start a new project in C4D and import the Vue file you just saved, via the Xstream plugin window within C4D. This is a bit of stuffing around especially if you still don't have your scene locked down but it is one option.

Chad P

[Bill-D]

thanks Chad P

I'll Checkout geekatplay for the tuts. The plugin within C4d will be the next mystery. I fear that by the time I 've learnt enough of Vue to function, Maxon will bring out the long wished -for Fluid dynamics and a useable Landscape/atmos module in R 11 (mac 64-bit as well)

This is pioneering stuff that your helping me with. Thanks again.

Bill-D

[Chadman]

No worries Bill, you'll be or right as l've only had Vue for about 4 weeks myself and l'm starting to grasp it and l'm no rocket scientist. :thumbsup:

Chad

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.