OTOH, if you mean a "Known Issues" thread, there's still this one (last updated 7/19/2019 by Nick).

@vkmast - I want an updated “VP17 Issues” Sticky. It’s now September 1. As you say, Nick last updated in mid July. And now we have issues and nobody is updating it. Strange that the one chap we have depended on is taking a well earned break, I assume, but over the period of the release of VP17? Come on MAGIX, get it sorted out and have an Issue Sticky for VP17.

@vkmast @Grazie This is long overdue and very important. Even the developers may be glad of it, unless they are diligently keeping track of all of the different bugs.

Another recent one ... https://www.vegascreativesoftware.info/us/forum/vegas-pro-17-mouse-issues-in-project-media-list-view--116981/

Maybe even start a new temporary thread listing the currently known issues and giving links to any relevant posts. This new VP17 thread could be subsumed eventually by Nick into the main “known issues” for VP17.

In the meantime it would serve as a reference to posters that think they may have a newly discovered bug thats well, not so new, for VP17 only.

@Former user - Exactly!!!

Maybe even start a new temporary thread listing the currently known issues and giving links to any relevant posts. This new VP17 thread could be subsumed eventually by Nick into the main “known issues” for VP17.

@Former user In fact, that's exactly what I intended to do, I have time for that, but I'm new to the forum and maybe not really legitimate.

@Former user In fact, that's exactly what I intended to do, I have time for that, but I'm new to the forum and maybe not really legitimate.

@Sylk - Well, apart us NOT knowing your real NAME, and that's up to you, but it would give some sense of legitimacy, you've made nearly 30 Posts in the last 24 Hours AND recieved a THANK YOU?! Potentially you've got my Vote unless there are others that wish to step up? Maybe a short CV expressing your committment to VP and Video Editing in general? You could start off with a Sig telling us your Rig and experience.

Bottom line here is that we need a Bug List created now. Nick's formaat is a good way to take forward.

@Sylk @Grazie Go for it whydat. Create a new thread, say VP-17 Known bugs/issues so far, whatever.

Main idea I think is that it should be more a list of issues with links to threads rather than for it to get bogged down with discussions for the individual topics, that should be for the separate threads, my 2 cents.

@Sylk - Well, apart us NOT knowing your real NAME, and that's up to you, but it would give some sense of legitimacy, you've made nearly 30 Posts in the last 24 Hours AND recieved a THANK YOU?! Potentially you've got my Vote unless there are others that wish to step up? Maybe a short CV expressing your committment to VP and Video Editing in general? You could start off with a Sig telling us your Rig and experience.

@Former user Honestly, my real name will not help you (to know me better), but me, yes. As Zorro. ;)

I updated my profile, may it allow you to better define me.

@Sylk @Grazie Go for it whydat. Create a new thread, say VP-17 Known bugs/issues so far, whatever.

Main idea I think is that it should be more a list of issues with links to threads rather than for it to get bogged down with discussions for the individual topics, that should be for the separate threads, my 2 cents.

@Former user Yep, i think categorize, at least in 3 kinds of issues ;

Major, causes crashes with frequently used tools.

Boring, limits workflow with totally unusable rare tools

Minors, reduces the comfort of use, but whose function is reachable by other tools.

Thanks for your support, i'll do my best.

@Sylk "JN_ Honestly, my real name will not help you (to know me better), but me, yes. As Zorro. ;)"

I'm sure you meant @Grazie here, he's of the inquisitive type.

Best of luck.

@Former user Haha, no, simply that my real name doesn't appear nowhere on the web, so useless for evaluate me.

After an unavoidable hiatus I'll be back at base in a couple of days and hope to make some updates to the "known issues" thread (& other FAQ threads) shortly thereafter. In the meantime if anyone cares to compile links to any VP17 known issues it would help me get up to speed.

Thank you Nick!

Maybe worth to mention about adding Magix in Nvidia Control Panel, in case some may have overlooked this step.

Techgage covers this in their latest look at VP17. https://techgage.com/article/magix-vegas-pro-17-cpu-gpu-performance/

Just remember that step is only meaningful if you're making your Magix settings different from your global settings... otherwise you can just enable or disable specific features on the global tab. The author in that article never shows us what his global settings are so it's not clear why he had a need to single out Magix on the application tab... and in all the screen entries we can see he leaves the global settings unchanged anyway. I imagine it only becomes significant if your global settings are optimized for gaming or some other video editor and you want those tweaks disabled or others enabled when you fire up Magix.

The global settings don't matter, because adding the profile even with 100% default settings still fixes it. In VP16, this affected some GeForces, but in VP17, I've only seen it impact Quadro and TITAN. I talked to MAGIX before the article was posted, and it's well-aware of the issue. I have a feeling the quickest fix would come from an NVIDIA driver update, but I'm not certain. Either way, I will do a bit of retesting once the next VP17 build comes out and see what might have changed. 

The global settings don't matter, because adding the profile even with 100% default settings still fixes it. In VP16, this affected some GeForces, but in VP17, I've only seen it impact Quadro and TITAN.

Have only tested it on a laptop with internal geforce gtx1050Ti + uhd630 and it made no difference there. Also tried out the 431.70 studio driver on that machine. Performance really went down the tubes across the board with qsv renders turning in the the same times as mainconcept and nvenc slowing down by about 15%.... likely perhaps because there is no dch package in a studio driver version yet. Reverting back to a dch game-ready package, I saw no impact with or without the PhysX api so I left that off. One thing I noticed was that checking the middle selection in Adjust Image Settings with Preview had a large positive impact.

The global settings don't matter, because adding the profile even with 100% default settings still fixes it. In VP16, this affected some GeForces, but in VP17, I've only seen it impact Quadro and TITAN.

Have only tested it on a laptop with internal geforce gtx1050Ti + uhd630 and it made no difference there. Also tried out the 431.70 studio driver on that machine. Performance really went down the tubes across the board with qsv renders turning in the the same times as mainconcept and nvenc slowing down by about 15%.... likely perhaps because there is no dch package in a studio driver version yet. Reverting back to a dch game-ready package, I saw no impact with or without the PhysX api so I left that off. One thing I noticed was that checking the middle selection in Adjust Image Settings with Preview had a large positive impact.

When I said global settings don't matter, I meant in this particular instance since it was the default configuration. I don't change settings and then not tell people about them. It could be that on certain setups, other options will need to be changed, but that's not something I've witnessed. But, I am just a benchmarker, not an actual user of the software. 

As I mentioned, GeForce doesn't seem to be affected right now, and in personal tests, adding the profile didn't change performance for those. It doesn't even change performance for everything on the impacted cards; it's most noticeable with LUT. 

With regards to the Adjust Image Settings, do you mean you selected "Use the advanced 3d image settings"? Because that is default. And in what way did it offer an improvement? Playback?