Opened 15 years ago
Closed 15 years ago
#4294 closed enhancement (fixed)
[feature-request] Please improve debugging and logging (vbox.log) for OpenGL -> Fixed in SVN.
| Reported by: | Technologov | Owned by: | |
|---|---|---|---|
| Component: | 3D support | Version: | VirtualBox 2.2.4 |
| Keywords: | Cc: | ||
| Guest type: | other | Host type: | other |
Description
VBox lacks a debugging for OpenGL in vbox.log...
I would like to see which OpenGL extensions are available on Host, and which are forwarded to guest (similar to CPU flags). This can be logged once OpenGL driver is loaded by guest.
This is important because on different Host OSes, same graphics card may have different features due to different drivers.
-Technologov, 24.6.2009.
Change History (3)
comment:1 by , 15 years ago
| Summary: | [feature-request] Please improve debugging and logging (vbox.log) for OpenGL → [feature-request] Please improve debugging and logging (vbox.log) for OpenGL -> Fixed in SVN. |
|---|
comment:3 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I've added extensions dump on the host as it could be usefull indeed.
Regarding the ones which are forwarded to guest, it's an intersection of extensions supported on host and extensions supported in our code + some additions. It's not something which may vary as it's limited by the code and will just pollute the host log. In case of need one could run glxinfo or glewinfo on the guest to see this list.
Also, note that running host VM with CR_DEBUG=1 env set, will dump more information to the host log.