Plugin failing when trying to render in Vegas pro 22

After going through the forums, I was finally able to get Voukoder to appear in my list of options for rendering in Vegas Pro 22, but when I set up the scene and tried to render it just gives me an "Unable to start Voukoder Pro message with the following in the logs:

2026-06-30 01:41:36 (info)	[EncoderNode.cpp:142] Initializing video encoder: hevc_nvenc
2026-06-30 01:41:36 (info)	[OutputNode.cpp:151] Successfully initialized the output format.
2026-06-30 01:41:36 (info)	[Router.cpp:164] Initialization succeeded.
2026-06-30 01:41:36 (info)	[Router.cpp:176] ### PHASE: PRE-OPEN
2026-06-30 01:41:36 (info)	[EncoderNode.cpp:332] Registering 1 video stream(s)
2026-06-30 01:41:36 (debug)	[OutputNode.cpp:346] Registered stream 2db94e40-3e45-42d8-aaac-b4dd16bd983c:0
2026-06-30 01:41:36 (info)	[Router.cpp:187] Pre-open phase succeeded.
2026-06-30 01:41:36 (info)	[Router.cpp:188] ### PHASE: OPEN
2026-06-30 01:41:36 (info)	[EncoderNode.cpp:433] Opening video encoder plugin 'hevc_nvenc' with params '{"rc":"constqp","qp":23,"g":12,"bf":0}'
2026-06-30 01:41:36 (error)	[EncoderNode.cpp:442] Opening the encoder plugin failed with error code: -542398533
2026-06-30 01:41:36 (error)	[Router.cpp:194] Open phase failed: -11
2026-06-30 01:41:36 (debug)	[NetworkLicenseChecker.cpp:140] License responder stopped.
2026-06-30 01:41:36 (debug)	[NetworkLicenseChecker.cpp:140] License responder stopped.

I'm assuming this would be the helpful part of the log, but I'm not really sure at the same time. Any help would be appreciated

Looking at the trace logs it looks like it was unable to render with the format that I used from the template and when I changed it it started running just fine. I appreciate you pointing me in the right direction for this! In terms of getting it to appear in Vegas pro 22 after uninstalling the plugin I installed an older version loaded vegas pro up to confirm it showed up in the components list even though it didnt show up in the render options list. Then upgraded to the newest version from there and then it loaded fine and has been consistent for me. I would assume something with the old version creates a file that is missing from the new one unless upgrading to the newest version does a clean install of the plugin. I am on windows 11 and I used the two versions have been listed (2.0.14 and 3.1.9).