very odd:

1) tried to render portion of the clip last half, it worked

2) tried to render first half, it worked

3) realized my logo Track Motion location was off, adjusted and then render whole 15sec, it failed at a different percent:

@KTY @Limit22

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

I wish there was as script for that. I might commission someone to get that done just because I feel I will be asking for help in the near future. I have a project for business that I pray it doesn't get hung up. At the moment, I render each half and then combined them into another project to render again for what I want. I'm afraid to do as you ask, but that is only to find a temp solution and never fix the leak. I do appreciate your response, thanks.

You might want to try rendering via the often recommended on the forum free Voukoder render plugin - https://www.voukoder.org/forum/thread/783-downloads-instructions/ . It's a 2 step download - the app itself as well as the connector for Vegas Pro 20.

Search the forum for Voukoder comments over the years to allay any concerns.

Mine will crash rather than render when I'm using the Color Grading plugin.
Vegas Pro 20, Win 10-64 on Intel i5 6400

@Patrick-Bryant

@Limit22

@KTY

With the inputs you gave us, do you really think that one is able to know what is going on on your machines?

@KTY @Limit22

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

Perhaps this part (important-information-required-to-help-you--110457) from the link 👆 provided needs to be highlighted?

Ich bitte dich um Vergebung.

Extra Information
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\fileio_x64.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\persist.prefs
   File:                C:\Users\magic\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                C:\Users\magic\AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\dx_video_grovel_x64.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\svfx_video_grovel_x64.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\ocio_x64.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\dx_grovel_x64.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\vst_grovel.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\vegas_script_x64.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\gpu_video_x64.log
   File:                C:\Users\magic\AppData\Local\VEGAS Pro\20.0\hub.log
   File:                E:\McCmedia\woodshed\MyPerformances\willitrender.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 20.0 (Build 370)
   Problem:             Unmanaged Exception (0xe0434352)
   Fault Module:        C:\WINDOWS\System32\KERNELBASE.dll
   Fault Address:       0x00007FFC070CCD29
   Fault Offset:        0x000000000002CD29

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 20.0\vegas200.exe
   Process Version:     Version 20.0 (Build 370)
   Process Description: VEGAS Pro