When I click on Pattern editor in Omnitiles, Max crashes.  

  RSS

Active Member Customer
Joined:8 months  ago
Posts: 5
28/05/2017 9:01 pm  

Just bought Omnitiles and finally got around to trying it out. I wanted to create a basic Stretcher bond brick wall. I loaded the pattern, assigned it to the plane everything was fine. I clicked on Pattern editor and Max crashed


ReplyQuoteLike
Estimable Member Admin
Joined:7 years  ago
Posts: 156
29/05/2017 10:52 am  

Hi Andrew,

thanks for reporting this and sending us a support ticket. We are working on this problem and will hopefully find a solution soon. 

Sorry for this frustrating experience.

Best regards,

Martin

 


ReplyQuoteLike
New Member Customer
Joined:2 years  ago
Posts: 4
30/05/2017 10:30 pm  

Exactly the same happens to me on both 3ds max 2017 and 2018, maybe it needs pointing out I use 4k display with 200% windows scaling - not sure if it might be related but who knows for some aps are kind of flaky with that. 


ReplyQuoteLike
 JD
Trusted Member Customer
Joined:6 years  ago
Posts: 59
31/05/2017 1:53 pm  

If you are using 3dsmax 2013/2014 there is a chance you might be hiting a problem with the creation of some logging file. A logfile is normally created when opening the pattern editor but it looks like the parrent directory of its location isn't created beforehand. The directory is c:\user\your_windows_user\appData\local\VIZPARK

You can either try to create that directory manually or use any of the other VIZPARK plug-in which will create this directory or if you have any other 3dsmax version installed Omnitiles for this version.

We are going to do a patch for this problem using 2014 soon.

Not sure about 2017/2018 that should definitely work and the windows scaling shouldn't matter. We've tried different scaling settings in the past. Please submit an issue/support request for that so we can follow up on it. Thank you!


ReplyQuoteLike
New Member Customer
Joined:2 years  ago
Posts: 4
01/06/2017 5:35 pm  

Hi again, in my case your suggestion of creating of c:\user\your_windows_user\appData\local\VIZPARK helped with the pattern editor crashing - it probably was because my windows was more or less freshly installed and there were no vizpark plugins installed prior to that so that folder wasn't there already, well anyway that solves the issue completely so thanks for that. 

Yet there's another one I ran into  https://www.flickr.com/photos/119850875@N05/34644814610/in/datetaken-public/ - what needs mentioning besides it is 4k (tv 4k 3840 × 2160 to be precise)  with windows scaling set to 200% is what it is windows 10 creators update and it did change something about app scaling if I'm not mistaken so, thanks to this "wise" meddling on Microsoft's side you might need to recheck the scaling compatibility of your plugins UIs in that environment anew .

The editor windows itself is quite small too, which of course would be much better if it could scale to 200% as well as the rest of 3dsmax, but it is tolerable at least when working on some large screen as I do (55inch tv that is)) but that superfat scrollbar and whacked up settings window surely needs some mending )) As you can see from that screenshot corona's vfb suffers from being unscaled as well but at least no scroll bars there to make it unusable.

 


ReplyQuoteLike
New Member Customer
Joined:5 months  ago
Posts: 1
15/08/2017 2:37 pm  

Same problem over here, just bought the plugin and it crashes in max2018 and max2017 as soon as you click on the pattern editor. Any solution yet? 


ReplyQuoteLike
 JD
Trusted Member Customer
Joined:6 years  ago
Posts: 59
16/08/2017 12:36 am  

Yes sorry the reason is that it is trying to write a logfile but it looks like the underlying directory hasn't been created.

User that had a previous or a different VIZPARK product installed probably do have this directory and therefore do not have this problem or why we didn't come across this before.

Try to create manually a directory in c:\users\your_windows_user\appData\local\VIZPARK

if that doesn't already exist. If it doesn't that is most likely the source of the problem.

Sorry for the inconvenience 


troubleman liked
ReplyQuoteLike
New Member Customer
Joined:5 months  ago
Posts: 2
16/08/2017 3:16 am  

The above suggestion of making a local VIZPARK  worked. Thank You. I hope this is fixed in an update as I just brought this 2 minutes ago only for it to crash in 3d max 2018.


troubleman liked
ReplyQuoteLike
New Member Customer
Joined:6 years  ago
Posts: 3
02/11/2017 9:26 am  

c:\user\your_windows_user\appData\local\VIZPARK

 

testing


ReplyQuoteLike
 JD
Trusted Member Customer
Joined:6 years  ago
Posts: 59
09/11/2017 1:29 pm  

Yes the next update of Omnitiles will certainly fix this issue.


ReplyQuoteLike
Active Member Customer
Joined:5 years  ago
Posts: 8
12/12/2017 11:44 am  
Posted by: JD

Yes sorry the reason is that it is trying to write a logfile but it looks like the underlying directory hasn't been created.

User that had a previous or a different VIZPARK product installed probably do have this directory and therefore do not have this problem or why we didn't come across this before.

Try to create manually a directory in c:\users\your_windows_user\appData\local\VIZPARK

if that doesn't already exist. If it doesn't that is most likely the source of the problem.

Sorry for the inconvenience 

Tried that as well on 3dsmax 2016.

Seems to solve it for me 🙂

 


ReplyQuoteLike
 JD
Trusted Member Customer
Joined:6 years  ago
Posts: 59
14/12/2017 6:36 pm  

Glad to hear this solved it for you, we're going to release an update hopefully soon that fixes the issue for everybody 🙂


ReplyQuoteLike
  
Working

Please Login or Register