Frequently Asked Questions
Q: How do I receive my cryptographic license key after subscribing?
The exact millisecond your transaction clears via our secure global merchant checkout rails, Lemon Squeezy will automatically generate a unique, single-seat license token and email it directly to your registered checkout inbox.
Q: How do I activate my license key inside the Command Dashboard?
Nexus utilizes an airtight, local profile-isolated execution scope. To activate your parallel compute channels, follow these simple structural steps:
1. Open your Windows File Explorer and navigate to your local profile suite folder path at AppData\Local\NexusVirtualGPU_V2\ (or NexusVirtualGPU\ for Standard Pro).
2. Right-click inside the folder, create a fresh plain text file, and name it exactly: config.ini
3. Open the file inside Notepad, paste your unique key, and structure it using this precise layout block:
[License]
Key=YOUR-SECRET-LEMON-SQUEEZY-KEY-HERE
4. Save and close the initialization file, then launch your dashboard panel to clear the cloud guardrail barriers.
Q: Can I share my license key across multiple computers?
No. Every license key is mathematically bound to a single hardware seat limit allocation to prevent international piracy loops. To activate Nexus on multiple workstations simultaneously, you must acquire additional individual user seats.
Q: How can I verify that Nexus is actively communicating with my web browser?
Initialize Google Chrome onto any active graphics template or 3D view, click 'Force-Inject' inside your Nexus dashboard command panel, and execute this system query command line inside a native Windows PowerShell terminal:
Get-Process chrome | ForEach-Object { $_.Modules } | Where-Object { $_.ModuleName -eq "opengl32.dll" }
The console grid will instantly return your local module file mappings, proving with absolute bit-for-bit certainty that Chrome has swallowed our driver shims straight into its runtime execution thread pool.
Q: My license key is valid, but the dashboard reports an 'Authentication Failure'. How do I resolve this?
This is almost always caused by a standard Windows text-encoding mismatch known as a UTF-8 BOM stall. When saving your initialization file, Windows Notepad can silently insert invisible formatting characters at the front of the file, which prevents the C++ parser from reading your token accurately.
To resolve this text-encoding quirk instantly:
1. Open your config.ini file inside Windows Notepad again.
2. Click on File in the top menu bar and select Save As...
3. Look at the bottom of the saving window panel right next to the Save button for the "Encoding" dropdown menu selection container.
4. Change the selection from "UTF-8" or "UTF-8 with BOM" and switch it strictly to: "ANSI" (or standard plain "UTF-8" without headers).
5. Click Save, overwrite the existing file configuration, and restart your dashboard. Your engine will now parse the clean alphanumeric values and pass the cloud guardrails natively!