Painting Creator issue, 2018 and 2019

[Davidk]

I use the painting creator tool (main tool bar, Tools\painting creator) frequently in my personal and class video work. In versions up to and including X10, it worked fine. But since 2018 was released, I have had trouble with it. Two cases cited below with screenshots taken in 2018:
- in a project file, being edited. Selecting an image for the purpose of adding a moving line on a map within the vsp failed, as (screenshot) llama farm 1 indicates.

- inserting that same (sacred valley) image into a "new project" after that failure also fails, in the same way.
- however, re-starting VS and as the first action in this session, inserting the scared valley image into the TL , selecting it and choosing painting creator works as advertised: screenshot llama farm 2.

I've reported this for 2018, and it very definitely was a 2018 "feature" - no such experience in X10 or X9 which are both still loaded on the same hardware. However no one has been able to replicate the response. Unfortunately, the new 2019 reacts exactly the same way. So I've experimented with things that might change the way elements of a vsp are processed such as the image sampling options (usually set to best and no letterbox) without any success.

It is very evidently a function of VS after a vsp is opened. If I attempt to create a painted map the very 1st action after opening VS, I get the right response, and while I had hoped that 2019 might rectify this, both 2018 and 2019 are responding identically top the same test sequences, outlined above. While one could say that hardware contributed, the fact that X9 and X10 both still function correctly opening painting creator on that vsp and image removes that consideration. Thus, clearly a software issue commencing with 2018.

What settings of VS preferences might cause this?

[asik1]

I'M sorry david,as far as I could understand your issue ... I don't have it on my2018.

[Davidk]

I have an HP g6-2002 laptop I use for my video studio classes: pretty much, I try to make sure only class material gets onto that machine. But in this case . .
I copied the test package to an SD card and used it to import the test package to the laptop. And it performed as the main desktop did - painting creator worked fine on an image in the vsp when it was running X10, and failed as reported when doing the same task (select image, choose tools\painting creator from main menu) using 2018. It worked using 2018 - as reported - if the photo being mapped was the first item into the TL after VS was started.
Both machines run win7, 64bit. The laptop has a 2.4ghz AMD A6 cpu and 8gb RAM, and the desktop has an Intel core i3 3.7ghz cpu with 8gb RAM.

It seems obvious that under normal circumstances, something in the 2018 and 2019 painting creator component programs doesn't like my hardware, whereas x10 and prior do. And that under special conditions, both 2018 and 2019 function OK on the same image. I think it has something to do with loading a saved vsp into the TL - like overwriting a memory cell - but its being elusive to track down a cause.