Idem pour avec moi une carte nVidia RTX3080. Les transitions se mettent en place, puis lors de la lecture apparait Invalid Shader et Vegas se bloque, puis ferme. Peut-être existe-t-il une astuce pour son emploi.

Merci pour votre réponse

Is your 3080 enabled under preferences/video?

Have an NVIDA RTX QUADRO 4000 GPU and yesterday after installing the new update, I too was getting the invalid shader and Vegas would crash. Didn't have time to mess with it but did check to be sure the GPU was enabled.

This morning, having of course rebooted ON, I went to Vegas to try again but this time started with the "bow tie" transitions and they worked, then the circles and they worked. Went to the top to try "Bounce" and that caused a crash. )No "invalid shader" message just a crash with the option to send message which I did. I'll go back and try some others and report back today or tomorrow.

Okay...had some extra time this morning and tried ALL of the GL transitions. I'm on Windows 10 Pro 64 and have an Invidia Quadro RTX 4000 enabled. ALL of the transitions worked just fine EXCEPT the following:

1. Bounce / Crash

2. Directional Warp / Crash

3. FlyEye / Invalid Shader

4. Hexagonalize / Crash

5. Swap / Crash

I went back to try Bounce again and it worked...BUT a few seconds later, crash.

The others seem to work just fine for me and some are quite nice indeed. Thanks Vegas Folk!

Maybe this will help isolate a particular issue?

@Bob-Harper I tried the ones you listed as problematic and they worked fine during timeline preview of them. No crashes. Using and old AMD RX480 8GB card with latest AMD drivers.

Cannot reproduce, I'm having an Nvidia RTX2080. Previewing and render up to 2160p50 with Magix NVENC HEVC and Voukoder, no issues.

Might be something with the Quadro specifically. Hopefully others can test.

Getting really good stability with this update. Had occasion yesterday to batch-render 23 song-regions in a large nested 4k multicam project. All good. After screening with talent, had to tweak 6 of them. Then while uploading 15 cleared ones to YouTube, I fired up 6 concurrent instances of Vegas, each rendering an individual region. Saw 100% cpu and gpu utilization, went to sleep, and woke up this morning to success. 6900xt / 11900k with latest AMD and Intel gpu drivers on Win11.

@Howard-Vigorita - Great results! Nests eh 😉.

@Grazie Thanks for your nesting suggestions... I'm still getting my feet wet. Only nested the graded multicam expansion into a project (with promoted regions ) so I could apply a watermark and put splits and fadeouts at the end of each song-region. Will try 2-level nesting from the grade level through a multicam track expansion tomorrow on the next day's shoot. Ha, ha, if that actually works I'll have to do a video on the technique.

Yes, we are aware of the crashing and "Invalid Shader" problems with GL transitions. We already have a fix that will appear in the next update. Unfortunately, with the holidays and team vacations, that won't be out for a while. I'm sorry this got through. Somehow it did not manifest either in our testing or in beta testers' testing.

Thanks for the update on the update Gary. Continued improvements and some holiday transition cheer. Thx.

Excited about the new transitions as I was having to use other programs for my preferred transitions, but as soon as I open a GL transition, Vegas crashes and closes. NVidia 1080TI.

@gary-rebholz - I'm not getting any issues with the list of Transitions mentioned above. Certainly no crashes here. I just re-tested:

1. Bounce > Working

2. Directional Warp > Working

3. FlyEye > Working no "Invalid Shader" Comment.

4. Hexagonalize > Working

5. Swap > Working

Maybe others would like to participate.

BTW : Great transtions

Maybe others would like to participate.

+1 All are working normal and fluent.

@j-v - Just preparing MP4s as Demo.

Bounce

Directional Warp

FlyEye

Hexagonalize

Swap

Appears fluid to me. I also moved the Control Sliders to give it a good test too.

Somehow it did not manifest either in our testing or in beta testers' testing.

@gary-rebholz - Not "manifesting" here.

Idem pour avec moi une carte nVidia RTX3080.

@gary-rebholz - @JCD has the same nVidia card as I.

Lot's of crashing since the update. Updated the Intel vid drivers a week before. Just working in multicam editing, panning, simple overlapping transitions. Nothing crazy. Not sure where to go from here. Just going to save every change I make until I can find a tweak to correct it. It was working relatively crash free, prior. I did have the Color Grading issue with a white diagonal artifact line. I was working with tech support about that a month ago or so. Have to see if this update fixed it.

I'm not saying there isn't a problem for some...obviously there is.

For those of you who see the crash or "Invalid Shader" when using GL Transitions, there is a workaround. For now, avoid using the Transitions window and hovering over presets. Instead do this:

1. Right-click the crossfade on your timeline
2. Choose Transition Properties from the context menu
3. Use the Plug-in-Chooser to add the GL Transitions
4. Select the preset you want from the Preset drop-down list in the Video Event FX window

Unfortunately you won't be able to preveiew the presets before you add them to your project, but you'll still be able to use the transitions.

I'm not saying there isn't a problem for some...obviously there is.

@gary-rebholz - I hope my testing and samples allow, Team-Vegas to have something of a fixed point for comparison. Here to assist 🙏 .

The problem is related to CPU usage and certain Nvidia Gfx cards that do not support OpenCL-OpenGL interops (and thus fall back to CPU usage). This is why some of you see no problems while others do.