Itoo Software Forum

Author Topic: Display method bug?  (Read 224 times)

JTP Vis

  • Full Member
  • ***
  • Posts: 107
Display method bug?
« on: September 06, 2017, 10:51:20 AM »
Hi,

We have for some time now noticed a Max crash associated with RailClone, but have been unable to pinpoint what is the root cause of it. It has generally been fixed by not using the "point cloud" method of displaying the objects, but recently I have been working fine with my RailClone objects displaying as point clouds. Until yesterday, when my file just wouldn't save, no matter what I did. Every time I went near the save button, CRASH... out went Max. This morning I asked my colleague to open the file to see if he could save it, and he did without a problem. It was at that point I noticed that he had the RailClone objects set to display as box, more importantly, degrade to box, not point cloud. It was then that I realised that what had changed in the scene was that I had added a new RailClone object that was set to box display as default, and it crossed my mind that perhaps the problem is actually with multiple RailClone objects displaying in different ways? So it was fine when the single object was set to point cloud, and fine when both were set to box, but when one was set to point cloud and one as box it seems to cause a rift in the Max-Save continuum!!

In this particular situation we are using Max 2017 and RailClone 2.7.5. I have not yet done any simple scene experiments to see if it can be reproduced always, as I have a very pressing deadline, but when I get time I will look further into it. I thought it was worth putting it out there to see if anyone else has the problem.

Cheers,

Bill

Michal Karmazín

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1429
Re: Display method bug?
« Reply #1 on: September 06, 2017, 11:04:16 AM »
Hi Bill,

Sorry to hear you're facing these troubles. Would you mind to save and send us  the minidump file of the crash?

Thanks in advance for any additional feedback on this issue you can share about it with us / our user community.

Best regards,

JTP Vis

  • Full Member
  • ***
  • Posts: 107
Re: Display method bug?
« Reply #2 on: September 06, 2017, 12:59:42 PM »
Hi Michal,

I've sent the minidump file (I hope it is the right one and contains the right information!!) via WeTransfer.

Please let me know if you need anything further. If this is not pertinent to the crash, I think I can make it happen again, to make a new crash and a new minidump... this is of course where it would not crash again, but please let me know what you find.

Cheers,

Bill

Michal Karmazín

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1429
Re: Display method bug?
« Reply #3 on: September 06, 2017, 01:48:30 PM »
Hi Bill,

Thanks for the provided minidump file. It's pointing to the PenIMC_v0400.dll, which is linked to Windows Pen & Touch support. As mentioned for example on this web-site, it's known problem and Microsoft is working on it. I'm afraid we can't much more in this case. Thanks for your comprehension.

If there will be anything more we can help you with, please let us know. Have a great day.

Best regards,

JTP Vis

  • Full Member
  • ***
  • Posts: 107
Re: Display method bug?
« Reply #4 on: September 06, 2017, 02:53:09 PM »
Hi Michal,

I am again very impressed with the speed with which you guys respond to problems reported! The website you pointed me to was very interesting as it points to the problem with the "Creator's update" for windows 10. This happens to be an integral part of the Win 10 install on this machine, and it has a number of problems related to it. It looks like it has a rather large number of issues pertaining to it, and if it gets "fixed" will solve a number of my current problems.

Thank you again for the swift and helpful responses, and I look forward to windows sorting their stuff out :-)

I suppose the good thing is that we can work around it in this instance, so it's not a major problem. Perhaps this post will assist someone else.

Cheers,

Bill