v17 install fails on windows 10 with danish locale

digilyd wrote on 8/12/2019, 10:53 AM

It appears that a windows`10 foldername-variable (probably %users%) is not read correctly by the install:


After this install error - only OK is an option - the install concludes and as it is a manual the routine can not find it really shouldn't matter. But a test-render failed due to some module not being found.



The filename.mp4 is the name of the file it should render ro. Is another windows 10 variable also not read correctly?

Comments

j-v wrote on 8/12/2019, 11:22 AM

What you can try is
-1 before installing VP17 uninstall all of Boris
-2 install VP17
-3 install Boris again

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

digilyd wrote on 8/12/2019, 2:13 PM

Hmm … boris installed properly on this box in september 2018 … hmmm … never used it, which is why my concern for the error was not large, just a quirk that will get fixed …. gonna try your suggestion tomorrow. Thanks!

digilyd wrote on 8/13/2019, 2:18 AM

Boris uninstalled, V17 uninstalled, only V17 reinstall, no error message from Boris, so now that issue is, if not solved, at least parked for now. But render anything, nah ….



Trying to standard documents folder instead of my render-folder:



Trying another project:



Both projects render flawlessly in V16. So this is about a Boris install bug and a separate Vegas rendering bug.

j-v wrote on 8/13/2019, 2:26 AM

Look Here

Solution is to make your self made rendertemplates in former versions again in VPro 17.
 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

digilyd wrote on 8/13/2019, 3:41 AM

Thank you, I haven't tested and don't have time to do it right now, but it looks as the solution. It is baffling that it is an issue, but I understand that they have done a lot of work on graphics card assistance, so some pointer in the preset must be wrong. I'll wait with the tagging until verified ….

 

digilyd wrote on 8/13/2019, 1:07 PM

Yes, the solution is to skip Boris in the install and then define render-presets anew as they get relevant. Perhaps skipping Boris had not been required since it was the manual it couldn't find, but it is an annoying error. Ah well, it is "known and described in the literature" to get US English versions of the OS because somebody somewhere always goofs when it comes to codepage 865, but we should be past that stage now ….