See https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-make-my-video-preview-play-smoothly-in-vegas-pro--104624/ esp. sections 4 and 11a.

Those NB Transitions in VMSP 16 show up and work in VMSP 17.

Thank you for your answers, but actually the issue was not limited to preview : no transition in the rendering neither, and the small A/B picture of the transition was not working. I write "was" because today it works, even if I changed nothing... Mystery, but the result matters, so ...

... Well I was a bit too optimistic ! Transition seemed to be OK for a while, but after a rendering, back to the previous situation 🙁. In the "Transitions" sheet, all the "3D external modules" are shown with this dark and light grey grid, that seem to show they are off. All others are showing a brief display of the A -> B transition effect.

I am totally lost !!!

Can you help ?

Thanks !!!

Maybe you see it, but we ain't

Not easy to explain with words...

After many testing, it seems that the rendering process into UHD with NVIDIA codec "blocks" the system, by-passing these 3D transition features. After that render, it becomes impossible to use / tune these transitions again. The only option is to quit and re-launch movie studio.

Rendering with INTEL UHD seems to work, but takes very long to "calculate" these transitions and forces my HDD up to 100%. In the previous version (16), all was OK.

Not easy to explain with words...

A picture tells more than a thousand words, you can easy make pictures with the free Screenpresso: https://www.screenpresso.com/ and add them by the button on top of your answer.
So you have a Nvidia: which one and what is the exactly driverversion you try to use?

You are totally right, better with pictures, so here they are :

The transition window as it looks "normally" : , with an "active" icon displaying the behaviour of the selected effect

And how it looks after rendering :

In this situation, the preview does not work neither, and the rendered movie does not include the selected transition.

Here is my configuration : , and the NVIDIA driver :

But I used INTEL codec for the render, don't know if it helps ...

Last point : till last Sunday, I was on Movie Studio 16, no such issue...

Thank you so much for your time !

First update your Nvidia driver this way

and than you'll find this one

What your transition problem concerns, probably you use there a 3th party transition and for complaining you have to ask the producer of that transition, because I don't see those problems with my 3D transitions of VMS 17 and there are only 4 of them, look

@j-v "3D Fly Away" is in the NewBlue Transitions 5 Ultimate package, which came with VMS 16 P (and S) (as said twice above). Like you, I don't see those problems in VMS 17 P either.

@vkmast I know, but because the NB stuff slowed down my programs starting and were in the beginning full of faults, I deleted all of of it exept a NB Titler about 1,5 year ago. Not seen those problems again since that moment.👍

@j-v I know that you're not the greatest fan of their products.

Well, I couldn't guess all this, thanks a lot !

Uploading / updating NVIDIA driver (I did it already but with a "game oriented driver", not the "studio one. Don't understand the difference but looks a smart idea.

I will try again and then remove all this NB stuff if still NOK.

Latest attempts were getting worse and worse, with a freezing rendering or estimated time to render increasing endlessly, till I kil the process the hard way...

Thanks again !

Don't understand the difference but looks a smart idea.

There were a few posts on this forum from the developpers where they stated to work together with the Nvidia developpers for making the best drivers for NLE's. The Vegas developpers adviced always to choose the latest Studio drivers, also because they are not renewed as many times as the Game drivers.