FAQs

Why can’t I disconnect from an instant3Dhub session or connect to a different session?

The current version of the plugin only supports connecting to a single instant3Dhub session. Once connected to a session, the plugin cannot disconnect or switch to a different session. To connect to a new session, you will need to restart your game application or the Unreal Editor.

If you’re testing in the Unreal Editor, we recommend using the Play in “Standalone Game” mode. This starts your game as a new process, allowing you to connect to a new session each time.

This is a known limitation, and we are actively working on a solution for future versions.

I’m experiencing issues with the instant3Dhub Plugin, such as connection problems, unexpected behavior or runtime crashes. How can I get help?

Please generate extended logs by increasing the verbosity of some or all of our log categories. These logs will help identify the problem and assist in troubleshooting.

• For general bugs / unexpected behavior: LogInstant3DHub, LogInstant3DHubJSExecutor

• For connection related problems: LogInstant3DHubWebBrowser, LogInstant3DHubWebSocketBridge

Our default verbosity is Log. We recommend Verbose for development and debugging purposes. In rare cases VeryVerbose might be helpful, but be aware that this can dramatically increase the performance impact and the size of the logs when used with the LogInstant3DHubJSExecutor or LogInstant3DHubWebSocketBridge categories. Verbose logging is expected to have only a small performance impact.

To change the log level, use one of the default methods provided by Unreal, for example:

• Console Commands

  • General bugs / unexpected behavior:

    -LogCmds="LogInstant3DHub Verbose, LogInstant3DHubJSExecutor Verbose"
    

  • Connection related problems:

    -LogCmds="LogInstant3DHubWebBrowser Verbose, LogInstant3DHubWebSocketBridge Verbose"
    

  • Combined:

    -LogCmds="LogInstant3DHub Verbose, LogInstant3DHubJSExecutor Verbose, LogInstant3DHubWebBrowser Verbose, LogInstant3DHubWebSocketBridge Verbose"
    

• Engine Ini File Add the following section to one of the engine ini files in your project (e.g. Config/DefaultEngine.ini, Config/UserEngine.ini). Note that these files affect packaged builds.

  [Core.Log]
  LogInstant3DHub=Verbose
  LogInstant3DHubJSExecutor=Verbose
  LogInstant3DHubWebBrowser=Verbose
  LogInstant3DHubWebSocketBridge=Verbose
  

The log files are located as usual in <Application or Project Directory>/Saved/Logs/.

Send the collected log files and a description of your issue to your contact person at Threedy for further assistance.

Why does some geometry appear transparent even though it should be fully opaque?

This is a known issue in Unreal Engine 5.3 caused by the combination of Forward Shading and MSAA. To work around this, either disable Forward Shading or switch to a different anti-aliasing method. Alternatively, consider upgrading to a newer version of Unreal Engine where this issue has been addressed.

If the issue persists after making these changes, please contact us for further assistance.