OpenGL 4.6 not detected on ASUS ROG Zephyrus 2022 with Radeon 6700S

Hello,

I am experiencing an issue with Isadora where it fails to detect the correct OpenGL version on my system. Even though my laptop fully supports OpenGL 4.6, Isadora reports OpenGL 1.0 and refuses to start.

System Details:

• Laptop: ASUS ROG Zephyrus 2022

• GPU: AMD Radeon 6700S (dedicated)

• Windows 11 64-bit

• AMD Adrenalin Drivers: latest version installed

• Isadora Version: latest available (4.3.1)

• The issue occurs with both Isadora 3 and Isadora 4

Steps I have already tried:

1. Verified GPU and OpenGL support

   • In the AMD Radeon Software, OpenGL 4.6 is reported correctly.

   • OpenGL Extensions Viewer confirms OpenGL 4.6 is available.

2. GPU settings

   • Set Isadora to “High Performance” in Windows Graphics Settings. (I also tried to assign the other gpu which didn't help either.)

   • Set GPU mode to “Ultimate / dGPU-only” in Armoury Crate.

3. Administrator mode

   • Attempted to start Isadora as administrator.

4. Overlays and background software

   • Closed Discord, Steam, Radeon Overlay, MSI Afterburner, Nahimic, and all other background apps that might hook OpenGL.

5. DLL workaround (tried to force OpenGL DLL)

   • Unable to locate standalone AMD OpenGL DLL (amdvlk64.dll or atio6axx.dll) in the system or driver folders. Modern Adrenalin drivers appear to integrate OpenGL differently, so the classic DLL copy method does not apply.

6. Display testing

   • I also tried connecting an external display, as in the past this resolved this issue, but it did not solve the problem this time.

7. Compatibility checks

   • Verified Isadora is not running in compatibility mode.

   • Tried on the internal laptop display only, with no external monitors.

I've been reading several posts on here but nothing has solved this problem for me. Does anyone have any ideas, what else I can try?

Best regards 
Rio

@barrowcivic

The easiest way around this is to make the value that is being changed exposed to the outside of the user actor and sent in via an input.
You could also, separate your touch OSC input values even more. Capture your OSC inputs, and set Globals to these values. Then in your user actor use the get Globals to use the values.
Globals will persist between scenes. (however, you can run into cases where moving to a new scene resets your values because you load a set Globals actor with new initial values)

So really, I think the easiest option is to expose the input values. For true cross scene persistence, a background scene is the most powerful option (although a little more advanced).
see: Isadora 101 - #7: Activating Multiple Scenes

Hi, I have a User Actor that is having internal actor values changed via touch osc. (specifically timing on a Jump Actor) I can modify value with touch osc when I am on the current scene but when I switch scenes the User Actor has not "saved and updated all." 

Is there a way to auto update the User Actor or a better way of doing this I am not aware of? I am relatively new to Isadora so I very well could have just missed something.

@miketutaj said:

It just looked different than previous versions so I wasn't sure if was working correctly.

I mean, it looks different because there's a drawing bug so technically it's not working properly. It is just an indicator for data traffic though, so even if it wasn't flashing when active, all the data traffic would still be working, you'd just have to look elsewhere in the program to see that.

@eight

A possible workaround:

It only works if you select the scene in the Scene Select control, rather than in the Scene List at the bottom of the window. The transition time of the scene sending the OSC command must be set to at least 0.01 seconds.

This may not be exactly what you are looking for, but I hope it helps!

Best regards, 

Jean-François 

@eight

Due to the processing model in the Isadora scene, I think an exit scene trigger requires some thought, since it would need to occur before the final round of scene processing (at least one round more would be needed to use the output trigger). 

Currently, the closest thing I can think of is the python_finalize() function supported by Pythoner. 

The docs state: 

python_finalize() takes no parameters, and any value it returns is ignored.

So you can't use it to send value or trigger out, but you could have it Send Out an OSC message, that can be retrieved in a background scene. If you are managing your Lasers from a background scene, this could provide the signal you are looking for.

@gunther said:

n input of 1 second results in a sound loop of 4 seconds

 FUN

If anyone has files of their own that they want to share, feel free to post them here (or preferably, post them on the TroikaTronix Add-Ons Page and then put the link here).

@woland thanks a lot !

Best, 

Maxi

Control Panels are a very powerful feature in Isadora, and they can be essential for making a patch easy to use. For that reason, I gathered together a collection of resources for learning about Control Panels in Isadora (which you'll find below). This started out as a response to a different thread, but I figured it might be good to post it on its own.

1. Our Isadora 101 Control Panel Youtube Tutorial is the best place to start.
   1. Here's a much longer, in-depth recorded Control Panel-focused livestream by Mark Coniglio, the creator of Isadora.
2. The Isadora 4 Manual (current version at the time of writing this is from October 2024) covers the Control Panel in various places:
   1. Basic explanation of Control Panels on pages 184-198 (this needs to be updated but is still good information).
   2. Set Control Focus Actor is covered on page 718.
   3. Show-Hide Control actor is covered on pages 725-726
      1. Here's a Show-Hide Control actor example file.
      2. You can also dissect the complex logic that makes the IzzyCast Basic Template Files' Control Panel act like a full-on application with different views, settings panels, previews, etc.
   4. Controls Reference Section on pages 829-887
3. YouTube Mini Tutorials
   1. Searching for Actors and Controls
   2. Control IDs
   3. Show Value of Linked Properties
   4. Showing and Hiding the Control Panel
   5. Copying Controls between Control Panels
   6. Scene Select Control
   7. List Selector Control and the accompanying example file
4. Files to look at:
   1. The general Isadora Examples files has different Scenes with various Control Panels.
   2. My simple show file example
   3. My global projection mapping file
   4. My Scene-based cue text example file
   5. My Scaling Isadora Example File
   6. My Color Tracking Isadora Example Files
   7. My Simple Q Control Example
   8. My MIDI Show Control Scene-Navigation & Cueing System
   9. My CONTROLS Scene and Set/Get Global Values (HSL Adjust) Example
   10. Many of my example files on the TroikaTronix Add-Ons Page have Control Panels.
   11. Many of the official TroikaTronix example files on the TroikaTronix Add-Ons Page have Control Panels.
5. Lastly, if you want some live help, I personally hold a free 1-hour Isadora Lab via the professional AV community Office Hours Global. The lab is open to anyone (not just AV professionals) and is held via Zoom every Thursday from 7pm-8pm CET (since I'm in Berlin, Germany). Sometimes I help people with projects, sometimes I teach people more about Isadora, and sometimes I teach people about Isadora from scratch. What I do during any given lab is determined by who shows up and what they'd like and I enjoy teaching Isadora to people and helping them with projects regardless of their level of experience with Isadora. Here's the link to get into the Zoom Call: https://zoom.us/meeting/register/tJIocuqsqT8pHNHE6mRQ5gMvhUAwnAd5-I2s#/registration

Best wishes,

Woland