@CXHernandez I had the issue you were having. Their does seem to be an issue where Questa ONLY looks at LM_LICENSE_FILE to find *ITS* license file. To solve this, I specify the Quartus license using the dialog box's "License File" entry and specify the Questa license file using LM_LICENSE_FILE. If you have managed to get BOTH licenses in the same file, you MIGHT be able to specify JUST that license file in the LM_LICENSE_FILE variable, but it does not seem to be the case since you are getting a license error. Questa, I think was ALSO supposed to look at MGLS_LICENSE_FILE, but it appears not to ever look at this. I can't tell you how much of a problem this caused us when we were trying to initially run the simulator, only to find out that it supposedly couldn't check out a license (we do have a license server, so I point Quartus to that and currently point Questa to a self-generated license). We had a full license for modelsim, way back, and it didn't expire, but it doesn't work anymore it seems. At any rate, we'll eventually sort out our license. Just a note, you appear to have LM_LICENSE_File instead of LM_LICENSE_FILE as well, which also doesn't work.
@BertRAMAerts The issue I seem to be having is getting Quartus to compile the simulation library under Ubuntu 20.04. It appears Intel isn't willing to support this, but now it appears someone had success. I kept running into issues where vlog would not process the encrypted IP. It seems to do the following:
1) I open the dialog. I point the tool at "QuestaSim" and the executables location to the questa_fse/bin directory. I select the output directory then press "Start compilation". This always fails the first time and I have to modify the executables location to get it to take.
2) Once the compile starts, it fails with "Macro `<protected> is undefined which then reports a syntax error in protected region.
Did you run into these errors trying to build the simulation library? I am trying to build for a MAX10, which uses the file fiftyfivenm_atoms_ncrypt.v, which seems to be where this error appears?