[External] : Re: Enabling debug messages

[Kevin Rushforth]

In that case, my guess is that those really are enabled only for debug 
builds. You can build a debug build using "gradle -PCONF=DebugNative".

-- Kevin


On 9/14/2023 6:02 AM, Nir Lisker wrote:
> Thanks, I set it to 5. On startup it prints info such as
>
> (I) D3DContext::InitContext device 0
> (V) HARDWARE_VERTEXPROCESSING
> (I) D3DContext::InitContext: successfully created device: 0
> (I) D3DContext::InitDevice: device 0
> (I) D3DContext::InitDevice: successfully initialized device 0
> (V) CAPS_TEXNONPOW2
> (V) CAPS_TEXNONSQUARE
>
> but I don't see any DebugPrintD3DError or TraceLn1 output despite them 
> being higher severity. I also tried setting it to 2 and then no 
> additional output appeared. I added cout prints next to them so I know 
> they are being reached.
> Any ideas?
>
> On Thu, Sep 14, 2023 at 3:29 PM Kevin Rushforth 
> <kevin.rushforth at oracle.com> wrote:
>
>     export NWT_TRACE_LEVEL=N
>
>     where "N" is the trace level. See
>     modules/javafx.graphics/src/main/native-prism-d3d/Trace.h
>
>     Btw, you can ignore the part about it being only enabled in debug
>     mode. That env var is recognized in production builds as well.
>
>     -- Kevin
>
>
>     On 9/14/2023 4:27 AM, Nir Lisker wrote:
>>     Hi,
>>
>>     I see that the D3D c++ files can output debug info via various
>>     DebugPrintD3DError and TraceLn functions. How can this output be
>>     enabled?
>>
>>     - Nir
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/openjfx-dev/attachments/20230914/75e7db54/attachment-0001.htm>