Summary

Title:High DPi Monitors with scaling cause Ornatrix to crash the "QT" System
Category:Crash/Critical
Status:Fixed
Posted By:ScannerD ( Can Erduman )
Date Created:5 February 2020

Problem

Description:

I had several crashes using Redshift. So I contacted them. After some exchanges with logfiles, they came up with Ornatrix being the problem. Here is the Conversation + All Logs.

https://www.redshift3d.com/forums/viewthread/29478/P15/

Steps to Reproduce:

System Specs:
Win10 64-bit

R21.115
RS 3.0.14
GTX 1080ti, GTX1060
Cintiq 24 Pro 3840x2160 (scale 175%), Samsung Syncmaster 2560x1440 (scale 125%)

Ornatrix + Redshift seem to cause the crash.

Hi Can,

Thank you for the report. I don't have the right hardware environment to reproduce this but the team will investigate this based on your info and logs. For reference for other users, please post a description of the issue here as well. Thanks! 

Jeordanis Figuereo (Product Designer. EPHERE Inc.)

Indeed, Ornatrix initializes Qt with a special parameter dpiawareness=0. This was needed until R20, without it we had problems.

Now probably R21 has changed its attitude towards DPI awareness, so we'll try to remove the option for R21. Please try the next nightly build of Ornatrix (22422 or higher) and let us know what difference does it make for you, if any.

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

Yes.  R21 finally got compatibility to high dpi. Took quite long. I will try to check it, tomorrow!

hThanks for the quick response!

 

Oh I can t find the 22442 Build. Or did you mean 22441?

A new nightly build is already out, try 22489. 

Jeordanis Figuereo (Product Designer. EPHERE Inc.)

Did some rendering! It looks good. The Redshift GUI seems much more responsive!

Aaaand it crashed. I clicked around a bit too harsh. Here is the Bug Report:
https://www.dropbox.com/s/wymbtkrm2wwop7v/_BugReport_OX_22489_Redshift.zip?dl=0

I can only read the .txt file, don't know what to do with the others.

In that file Ornatrix is not present in any of the call stacks. Does the crash happen if you don't use Ornatrix in the scene?

Do you think the crash is related to the multi-monitor setup with non-100% text scaling? Does it disappear if you use a single monitor at 100%?

If it's not related to the multi-monitors, it would be easier for us to reproduce, if you provide your scene and steps how to reproduce the crash.

Also, I see in the .txt file that Redshift has its own copy of Qt included, with -Redhshift suffix in the names of the .DLLs. This might be causing problems too, and if it indeed does, I think it would be impossible to work around.

 

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

I see in the .txt file that Redshift has its own copy of Qt included, with -Redhshift suffix in the names of the .DLLs. This might be causing problems too, and if it indeed does, I think it would be impossible to work around.

Iv reported an IPR issue with Redshift and Redshift have replied to me and said its the Qt conflict with Ornatrix.  Are you saying that if its the QT its impossible to work around, and if so then that also means Redshift is not compatible with Ornatrix, this is what Redshift told me.

"If you have Ornatrix please remove it as it conflicts with our QT"

Dan

My Web Site -  ArtStation

We'll get in contact with Redshift developers to try to resolve the issue.

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

That's a good decision. Removing ornatrix was a difference between night and day

 When using the redshift IPR. I reinstalled the newer version of ornatrix without Qt. And it behaved also very good.

However it crashed! I can't say, if it's a rs or ox crash.

Hi Can,

To investigate the crash you're running into, we'll need some more info from you.

As a first step, can you try the hack I suggested to Daniel in the other thread:

https://ephere.com/plugins/autodesk/max/ornatrix/defect_13179.html

That is, rename Ornatrix.xdl64 to z_Ornatrix.xdl64 so that it gets loaded after Redshift, and see if this will make any difference in Redshift's behavior.

If you still get a crash, please upload here the OrnatrixC4D.log file from your %TEMP% directory, along with the _BugReport.txt file from the report you uploaded eariler (btw, where do you get that report from? Does C4D create it?)

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev

The V1 nightly build (23767 or later) no longer uses Qt at all. Please test it with Redshift IPR.

Ivan Kolev (Software Developer, EPHERE Inc.)

E-mail: ivan.kolev at ephere dot com

Discord: ikolev