Re: FOX 1.7.78 OpenGL not working?

Understand.  I am not complaining about that  :-)

- Just trying to figure out - why with the same VM environment, gltest 
was working with Fox version 1.6.57.  Now it stops working with Fox 
version 1.7.78 for the same VM.
- I use VM for development/testing my SUMO project. And with version 
1.7.78 SUMO won't work inside the VM environment at all.
- I need to mention - on a NON-vm environment, i.e., a physical 
computer,  gltest build with Fox v1.7.78 works just fine.

Any insights or hints would be appreciated.

Thanks again
Wuping


----- Original Message ------
From: [email protected]
To: "Wuping Xin" <[email protected]>
Cc: "FOX Users" <[email protected]>
Sent: 8/18/2021 4:25:28 PM
Subject: Re: [Foxgui-users] FOX 1.7.78 OpenGL not working?

>On 2021-08-18 14:26, Wuping Xin wrote:
>>Greetings JVZ,
>>
>>Sorry My bad.  In the previous email, I attached two snapshots - not
>>sure if you were able to view it.
>>
>>Here are more information:
>>
>>-  I used the gltest project that is included in the FOX code base
>>-  Windows Server 2016 (on a VMWare Virtual Machine),  Visual Studio
>>2019; but on the SAME virtual machine,  gltest project compiled with
>>Fox version 1.6.57 work normal.
>>-  I tested the gltest project both 32 bit and 64bit,  and both Debug
>>and Release.  The issue seems prevailing on all of them
>>-  I didn't make any changes to the source file, compiler flags, or
>>preprocessor macros
>>-  I haven't done any further tracing work (yet, I am still learning
>>Fox but I'd love to be helpful and contributing once I can)
>>-  I sent out the email just to check if it is known or someone else
>>has already encountered the same.
>>
>>I suspect the OpenGL driver (that comes with VMWare ?) somehow is
>>"incompatible" with Fox v1.7.78.  It works with Fox v1.6.57, though.
>>That is why I wonder what has changed between the two versions.
>
>Well, if you're running inside a VM, you very likely won't be able to
>get full 3D performance, if it even works!  I believe direct H/W access to card and drivers is required, and those are walled off by the hypervisor.
>
>   -- JVZ