THE TESTENING - The Splittening - .NET 9 graphical client build

[Frooxius]

Hello everyone!

It's time! The Splittening - the last phase of our "Big Performance Update" is ready to start testing!

It's not complete yet - there's still a chunk of things that need to be implemented, polished and tuned - please check info below on what's missing, however it's in a state where it's beneficial to start checking of bugs and issues.

We're starting the testing with desktop only mode - VR does not work yet - but it will soon! However this is not necessary for initial rounds of testing.

Also the build is still being tuned! There's some weirdness with some performance issues that are being worked on. For an example you can check this devlog: https://www.youtube.com/watch?v=vTQdG3yqjFw&feature=youtu.be

Build Version

Please check the latest [PRE-RELEASE] build in #Updates on the Discord or the Updates post in this thread.

What is being tested

We're testing "The Splittening" - a joking name for separation of FrooxEngine and Unity into two separate processes. FrooxEngine now runs as .NET 9 process, which should provide substantial performance boost compared to Unity's Mono.

This is a drastic change in how the engine works with regards to rendering and we need to make sure it doesn't break any existing behaviors.

See here: #2429
And here: #706

General testing notes

TEST THESE BUILDS AT YOUR OWN RISK

These are a prerelease builds, meaning the implementation is INCOMPLETE and likely contains bugs. Since VR is a lot more intense, if you suffer from PHOTOSENSITIVITY, I strongly ADVISE AGAINST TESTING these builds, especially in VR. Bugs can cause BRIGHT FLASHES and other CORRUPTED VISUALS! Let people who are not sensitive to these test this first!

Please note that these builds ARE NOT early access to the splittening - they are INCOMPLETE and do not represent the final state of the software. I do not recommend doing any conclusive benchmarking and drawing conclusions at this point, since there's a number of debug mechanisms and bugs that mess with performance and can severely degrade it.

Local database location

The prerelease uses separate local database due to slight incompatibility between LiteDB with .NET 9 and Mono. You will need to do a fresh login and you'll have a fresh local. I don't recommend using those permanently as the database will be switched back to main location on release.

---

The structure of the build is also now changed somewhat:

• The main "Resonite.exe" is now .NET 9 process similar to headless
• Unity parts are in "Renderer" subfolder "Renderite.Renderer.exe"
  -- You NEVER run this .exe yourself, it's launched automatically
• There are now two processes - Resonite.exe and Renderite.Renderer.exe that will be running side by side

DO NOT overwrite your worlds/items with this build. There might be compatibility issues & data loss - always save a copy!

They are also not backwards compatible, so if you switch to the main build, they'll be broken.

How to test

The builds are on the prerelease branch.

• On Steam, switch to the prerelease branch and make sure the build updates before you run it
• Make sure your build version matches the one at the top of this message

NOTE: Currently you might need to install .NET 9 Desktop Runtime manually, because we do not have an install script yet. You can find it here: https://dotnet.microsoft.com/en-us/download/dotnet/9.0

If you're on Linux, you're currently on your own too until we make install script.

What to test

• Use Resonite. This is major change, so it's pretty broad.
• Load worlds, items
• Host sessions, play with people - some datatypes were moved
• Check all the already implemented "renderable components
  -- Check if their properties work as they do on the normal build - and if they transition properly when changed
• Check any items that reference values of any of the renderable components (e.g. Light modes, Reflection probe modes and so on)
  -- Did they convert properly to remapped types? Are they working as they should?
• Clipboard - copy & pasting
• Inputs - do they behave the same
• Does Resonite.exe or Renderite.Renderer.exe linger after shutdown or crash in some cases?

What are renderable components?

Here are some examples of components that are "renderable":

• MeshRenderer
• SkinnedMeshRenderer
• ReflectionProbes
• Lights
• AmbientLightSH2
• Skybox
• Textures (2D, 3D, Video...)
• Meshes
• ParticleSystems
• Cameras
• Mirrors / Portals
• HiddenLayers
• GaussianSplats

What to watch out for

• Crashes / Freezes
• State of renderer getting corrupted - e.g. meshes stop updating or update wrong
• Compatibility issues with saved worlds/items
• Regressions in any of the renderable components - functions that work on the main build, but not on pre-release
• You can benchmark things to see if there are any significant regressions - the more solid data/replication you can provide the better
• Processes not disposing cleanly

What NOT to test & report

• Any behaviors that are not yet implemented - please check the "What's Missing" section before you report!
• Any issues that are present on the main build already - we're not hunting for existing bugs, only newly introduced ones with this build!
• If in doubt, try to replicate the issue on the main build. Only make pre-release report if the bug happens on prerelease only!

If you find something that got broken

• Create a GitHub issue for a pre-release bug: https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/new?assignees=shiftyscales&labels=prerelease&projects=&template=prerelease.yml
• ALWAYS include FrooxEngine log & Unity log (Player.log)!
  -- IMPORTANT: Unity log is now under C:\Users\<your username>\AppData\LocalLow\Yellow Dog Man Studios\Renderite.Renderer
• Please include description of what happened. Be succinct, but exact

If you find that stuff works okay

Please report it too and include details on what you generally tested, so we know things are okay. You don't need to make a new issue for this - just a brief comment in this Discussion is fine.

How long will testing go for?

We plan to release this to main on this Wednesday (20th). All remaining issues will be sorted post release.

[KyuVulpes]

So, at this moment, Resonite does not launch using Proton. I have tried different versions of Proton and they all come back with the following image.

If I hit yes, it launches the site to install .NET. I am going to see to try and install .NET 9 through round-a-bout means. I think it should be built as self-contained.

[CheesecakeCG]

I got Resonite to boot finally by installing .NET 9 through Bottles.

I tried using ProtonTricks and with the .NET Desktop installer that clicking yes on that dialog takes to you to. It still does start for me. I tried Proton-GE-RTSP15 and Steam's Proton 9.0.
It dies with this stack trace in the proton log. The resonite log only has the date & time and nothing else.

101573.005:0130:0134:err:eventlog:ReportEventW L"Application: Resonite.exe\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"CoreCLR Version: 9.0.625.26613\n"
101573.005:0130:0134:err:eventlog:ReportEventW L".NET Version: 9.0.6\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"Description: The process was terminated due to an unhandled exception.\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"Exception Info: System.TypeInitializationException: The type initializer for 'System.Management.WmiNetUtilsHelper' threw an exception.\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L" ---> System.ComponentModel.Win32Exception (126): Failed to load required native library 'C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\wminet_utils.dll'.\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at System.Management.WmiNetUtilsHelper..cctor()\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   --- End of inner exception stack trace ---\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at System.Management.MTAHelper.IsNoContextMTA()\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at System.Management.MTAHelper.CreateInMTA(Type type)\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at System.Management.ManagementPath.CreateWbemPath(String path)\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at System.Management.ManagementPath..ctor(String path)\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at System.Management.ManagementScope..ctor(String path)\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at System.Management.ManagementObjectSearcher..ctor(String scope, String queryString, EnumerationOptions options)\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at Hardware.Info.Windows.HardwareInfoRetrieval.GetOs()\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at Hardware.Info.Windows.HardwareInfoRetrieval..ctor(Nullable`1 enumerationOptionsTimeout)\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at Hardware.Info.HardwareInfo..ctor(Boolean useAsteriskInWMI, Nullable`1 timeoutInWMI)\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at FrooxEngine.SystemInfo..ctor() in D:\\Workspace\\Everion\\FrooxEngine\\FrooxEngine\\Devices\\SystemInfo.cs:line 15\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at Program.<Main>$(String[] args) in D:\\Workspace\\Everion\\FrooxEngine\\GraphicalClient\\Program.cs:line 29\r\n"
101573.005:0130:0134:err:eventlog:ReportEventW L"   at Program.<Main>(String[] args)\n"

Full Log: steam-2519830.log

[KyuVulpes]

I forgot to enable Proton logging for myself. I am going to write an issue about this.

[ptelder]

I was able to get past this issue with a registry hack from https://techcommunity.microsoft.com/discussions/windowsserver/windows-server-2019-and-net-4-8/2660319/replies/3840420#M9922 - but that broke mscoree.dll

I've tried again with a blank prefix, but haven't been able to get past the wmiutils error again. Placing the correct .dll at that path doesn't alter the error.

UPDATE: After the most recent Resonite update (in the past hour or so) - it seems to have mutated to a platform not supported error:

2817.511:0140:0144:err:eventlog:ReportEventW L"Application: Resonite.exe\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"CoreCLR Version: 9.0.625.26613\n"
2817.511:0140:0144:err:eventlog:ReportEventW L".NET Version: 9.0.6\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"Description: The process was terminated due to an unhandled exception.\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"Exception Info: System.PlatformNotSupportedException: Could not find an installation of .NET Framework v4.0.30319. System.Management requires native modules from the .NET Framework to operate.\r\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"   at System.Management.WmiNetUtilsHelper.<>c__DisplayClass104_0.<LoadPlatformNotSupportedDelegates>b__39(Int32 _, IntPtr __, APTTYPE& ___)\r\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"   at System.Management.MTAHelper.IsNoContextMTA()\r\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"   at System.Management.MTAHelper.CreateInMTA(Type type)\r\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"   at System.Management.ManagementPath.CreateWbemPath(String path)\r\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"   at System.Management.ManagementPath..ctor(String path)\r\n"
2817.511:0140:0144:err:eventlog:ReportEventW L"   at System.Management.ManagementScope..ctor(String path)\r\n"
2817.511:0120:0124:trace:unwind:RtlGrowFunctionTable 00000000037F6B50, 124

This is on a fresh prefix with mono yanked and replaced with dotnet9.

[phil-flip]

I seem to run into a similar issue. I was able to install dotnet9 and dotnetdesktop9 packages through protontricks, but also run into the issue that it can't find wminet_utils.dll.
Apparently It's possible to get it with dotnet48(?) but, the support for it in proton doesn't seem to be the best anymore and a GitHub issue ingoing.. Funnily enough it does place them all into the correct folder but rolls the installation back and fails.

176131.499:0138:013c:err:eventlog:ReportEventW L"Application: Resonite.exe\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"CoreCLR Version: 9.0.24.52809\n"
176131.499:0138:013c:err:eventlog:ReportEventW L".NET Version: 9.0.0\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"Description: The process was terminated due to an unhandled exception.\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"Exception Info: System.TypeInitializationException: The type initializer for 'System.Management.WmiNetUtilsHelper' threw an exception.\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L" ---> System.ComponentModel.Win32Exception (126): Failed to load required native library 'C:\\windows\\Microsoft.NET\\Framework64\\v4.0.30319\\wminet_utils.dll'.\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at System.Management.WmiNetUtilsHelper..cctor()\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   --- End of inner exception stack trace ---\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at System.Management.MTAHelper.IsNoContextMTA()\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at System.Management.MTAHelper.CreateInMTA(Type type)\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at System.Management.ManagementPath.CreateWbemPath(String path)\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at System.Management.ManagementPath..ctor(String path)\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at System.Management.ManagementScope..ctor(String path)\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at System.Management.ManagementObjectSearcher..ctor(String scope, String queryString, EnumerationOptions options)\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at Hardware.Info.Windows.HardwareInfoRetrieval.GetOs()\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at Hardware.Info.Windows.HardwareInfoRetrieval..ctor(Nullable`1 enumerationOptionsTimeout)\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at Hardware.Info.HardwareInfo..ctor(Boolean useAsteriskInWMI, Nullable`1 timeoutInWMI)\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at FrooxEngine.SystemInfo..ctor() in D:\\Workspace\\Everion\\FrooxEngine\\FrooxEngine\\Devices\\SystemInfo.cs:line 15\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at Program.<Main>$(String[] args) in D:\\Workspace\\Everion\\FrooxEngine\\GraphicalClient\\Program.cs:line 29\r\n"
176131.499:0138:013c:err:eventlog:ReportEventW L"   at Program.<Main>(String[] args)\n"

[phil-flip]

I got further this time...

NOT A SOLUTION JUST STEPS TO GET TO THE ERROR I RAN INTO

1. Rename your existing "compatdata" folder for Resonite (2519830) to something else, so we can make sure we are starting clean.
2. Start the game with Proton 4.2-9
3. Wait for proton to download and close the game
4. Install dotnet48 with protontricks: protontricks 2519830 -q dotnet48 -v (I did it with the GUI, as I was unsure, why the winecfg kept opening.)
5. Hit OK on the Winecfg and install both installers normally. They should succeed
6. Switch back to Proton Experimental and start the game to make sure Steam does its job
7. Install dotnetdesktop9 and dotnet9: protontricks 2519830 -q dotnetdesktop9 -q dotnet9 -v
8. Observe the error in the proton logs

180276.494:0138:013c:err:eventlog:ReportEventW L"Application: Resonite.exe\n"
180276.494:0138:013c:err:eventlog:ReportEventW L"CoreCLR Version: 9.0.24.52809\n"
180276.494:0138:013c:err:eventlog:ReportEventW L".NET Version: 9.0.0\n"
180276.494:0138:013c:err:eventlog:ReportEventW L"Description: The process was terminated due to an unhandled exception.\n"
180276.494:0138:013c:err:eventlog:ReportEventW L"Exception Info: System.IO.FileNotFoundException: Could not load file or assembly 'C:\\Program Files\\dotnet\\shared\\Microsoft.NETCore.App\\9.0.0\\System.Runtime.dll'. Module not found.\r\n"
180276.494:0138:013c:err:eventlog:ReportEventW L"File name: 'C:\\Program Files\\dotnet\\shared\\Microsoft.NETCore.App\\9.0.0\\System.Runtime.dll'\n"

The file exists, but probably not loaded proper. I also tried installing dotnetcore3 and desktop, but that doesn't help.
EDIT: I also tried with the newest version (9.0.7) of dotnet9 and dotnetdesktop9.

[darbdarb]

KAYLA - 2025.7.8.73 - 2025-07-08 12_33_56.log
Player.log
Crash logs :3

[darbdarb]

@markusforever_
@Snuhr
joined me and crashed 3-5 seconds later after seeing radial menu

[brecert]

In the hour of testing I've done I can confirm most hitches are significantly reduced, worlds load faster, switching tabs has little performance drop.
I did not see any lingering processes after I finished testing.

UIX Flashing seemed to be much worse.

My resting FPS in worlds was nearly half what I would typically get with an uncapped framerate, I had trouble consistently reaching 120 fps in worlds I would easily reach that in normally. It may be related to frame timing weirdness or settings not being respected so I'll hold off making a more extensive issue for my reduced resting fps until those issues are resolved.

[Dusty-Sprinkles]

I can agree I observe much worse uix flashing, I shared a video of that in this issue #4563

[Frooxius]

2025.7.8.248 [PRE-RELEASE]
Hello everyone!

I got first two fixes for The Splittening build! I focused on the ones that prevent people from joining each other and one related that was made worse by some of the rework.

I'll be sorting through more soon, but I'm kinda tired, so I only managed to do this so far.

If you'd like to help testing, check this thread please: #4774

Fixes:
Fixed crashes when joining users due to race conditions (reported by @venport, @jvyden, @epicEaston197, @modern, @kulza, @kav, polyjitter, issue #4775)
Fixed closed worlds not getting cleaned up, sometimes resulting in remaining items

[Frooxius]

2025.8.19.222 [PRE-RELEASE]
Screenshots now save on Linux thanks to j4.lc! And more bugfixes! And locale additions and merges!

If you missed the #📢announcements post, we're now locked in for release on Wednesday, so a lot of the focus is on the most pressing issues for public availability, a lot of the smaller issues will be resolved post release.

WARNING CHANGE: Since things are now quite stable, we're lowering the epilepsy warning! It seems that issues with flashing lights due to bugs are pretty much gone, so it might be safer to test if you're photosensitive.

However these are still testing builds, so you might end up hitting a more rare bug in some cases - be on a lookout and prepared that things might still go wrong. If you want to be extra careful, wait for this to be fully released! But if you're okay with a small risk, I don't think it's much higher than at release builds at this point.

NOTE: The prerelease uses separate local database due to slight incompatibility between LiteDB with .NET 9 and Mono. You will need to do a fresh login and you'll have a fresh local. I don't recommend using those permanently as the database will be switched back to main location on release.

The goal of these builds is to find bugs and issues and fix them before public release for general use.

TEST AT YOUR OWN RISK

You can see status of the tasks here: The Splittening (view)

If you'd like to help testing check this post here: #4774

New Features:

• Screenshots and files can now be exported on Linux (implemented by j4.lc)
  -- Like on Windows, screenshots will go in a "Resonite" folder within your "Pictures" folder while exported files will go in a "Resonite" folder within your "Documents" folder

Tweaks:

• Added additional logging for issue by shadowpanther, issue The Dash's main screen gets reset every launch #5227

Locale:

• Merged new locale strings by ryuvi
• Merged English locale updates by modernballoonie, zyro1331, muppeq
• Merged Japanese translation of help tab by kazu0617, ginjake, zozokasu
• Merged French translation of help tab by baplar

Fixes:

• Desktop tab is now properly disabled on operating systems other than Windows (reported in Desktop tab not being disabled on Linux #5259 by bredo, fixed by j4.lc)
• Fixed Anisotropic filtering mode being handled incorrectly for videos, causing exceptions and issues with video playback due to missed/delayed updates (reported by foxbox., defhammer, j4.lc, issue Playback Driver Protoflux Node Breaks VideoTextureProvider #5274)

Known issues:

• Clipboard is not implemented for Linux yet (drag & drop works though)

[Frooxius]

2025.8.19.625 [PRE-RELEASE]
More bugfixes, tweaks and improvements! A lot of the stuff I'm wrapping up and getting stuff ready for release on Wednesday!

WARNING CHANGE: Since things are now quite stable, we're lowering the epilepsy warning! It seems that issues with flashing lights due to bugs are pretty much gone, so it might be safer to test if you're photosensitive.

However these are still testing builds, so you might end up hitting a more rare bug in some cases - be on a lookout and prepared that things might still go wrong. If you want to be extra careful, wait for this to be fully released! But if you're okay with a small risk, I don't think it's much higher than at release builds at this point.

NOTE: The prerelease uses separate local database due to slight incompatibility between LiteDB with .NET 9 and Mono. You will need to do a fresh login and you'll have a fresh local. I don't recommend using those permanently as the database will be switched back to main location on release.

The goal of these builds is to find bugs and issues and fix them before public release for general use.

TEST AT YOUR OWN RISK

You can see status of the tasks here: The Splittening (view)

If you'd like to help testing check this post here: #4774

Optimizations:

• Rewrote logging mechanism for graphical client to avoid locking on threads handling the logging & added log message indication
  -- The log file now has emojis to indicate message type :3

New Features:

• Added fail-safe logging mechanism for crashes that happen before logging system is fully initialized or when the logging system explodes
  -- This will create file Renderite.Host.Crash.<timesstamp>.log in the folder

Tweaks:

• Added icon to Resonite.exe file
• Updated Steam auto-firewall rule to the new main process name

Fixes:

• Fixed VRAM not being reported on Linux for AMD GPU's (reported by bredo, raidriar796, issue VRAM amount not reported on Linux #5217 fixed by gawdl3y)
• Fixed regression inviting users to sessions you don't host not working (reported by bredo, canadian_redz, yoshiyoshiyoshiyoshiyoshyoshyosh, zyro1331)
• Improved bootstrapper lifecycle
  -- Main process will now explicitly shut bootstrapper down on exit, rather than letting it timeout
  -- Increased timeout to avoid early shutdown
  -- Added timeout to initial launch to prevent Resonite.exe process lingering on failed Renderite.Host.exe launch indefinitely
  -- On Windows, the bootstrapper will shutdown automatically when the main process ends
• Re-added cursor position lock-in when cursor position is locked (this might fix cursor being jittery when rotating things reported by kawwwabi, baplar, ultrawidegamer, papaltine, bd_, ssmucny, luxkitty, brecert, issue Item rotation jittery on desktop #5157)

Known issues:

• Clipboard is not implemented for Linux yet (drag & drop works though)

[Frooxius]

2025.8.19.1372 [PRE-RELEASE]
A few more fixes!

NOTE: The prerelease uses separate local database due to slight incompatibility between LiteDB with .NET 9 and Mono. You will need to do a fresh login and you'll have a fresh local. I don't recommend using those permanently as the database will be switched back to main location on release.

The goal of these builds is to find bugs and issues and fix them before public release for general use - however since we're very close to release, these are mostly there for general use.

TEST AT YOUR OWN RISK

You can see status of the tasks here: The Splittening (view)

If you'd like to help testing check this post here: #4774

Fixes:

• Fixed off-by-one error when aligning requested texture size to available mipmaps, causing some textures not to load properly (reported by luxkitty, issue Some Uncompressed Textures Not Loading in Prerelease #5305)
• The Steam API library is now initialized properly on Linux, making it possible to export screenshots to Steam again (reported by mxjessie, issue Steamworks doesn't load on Linux, which breaks saving photos to disk #5177)

Known issues:

• Clipboard is not implemented for Linux yet (drag & drop works though)

[Frooxius]

2025.8.20.332 [PRE-RELEASE]
Polishing up a few more things. I was hoping to sort out a few more issues before the release, but my phone broke at the worst time, so I spent a bunch of time setting up my old phone and moving stuff to it :( (can't push a new build to release without confirming on my phone).

We've also ran into issues with SDL3 clipboard for Linux, where it just... doesn't work. We're currently working on alternate solution to get at least text copy & paste on Linux.

NOTE: The prerelease uses separate local database due to slight incompatibility between LiteDB with .NET 9 and Mono. You will need to do a fresh login and you'll have a fresh local. I don't recommend using those permanently as the database will be switched back to main location on release.

The goal of these builds is to find bugs and issues and fix them before public release for general use - however since we're very close to release, these are mostly there for general use.

TEST AT YOUR OWN RISK

You can see status of the tasks here: The Splittening (view)

If you'd like to help testing check this post here: #4774

Tweaks:

• Updated yt-dlp to latest version to resolve videos not loading (reported by luxkitty, sylphsylvia, moonbase__, j4.lc, epiceaston197, brecert, ohzee, CaelThunderwing, gawdl3y, bredo, MahSandwich, issue Youtube Videos No Longer Loading At All #5309)
• Updated Help screen to latest version (updated by ryuvi and aegis_wolf)
• Added additional logging for videos to help diagnose issues

Locale:

• Merged Chinese locale update by modimobeikete
• Merged German locale update by muppeq
• Merged Esperanto locale update by sejden
• Merged Russian locale update by troyborg
• Merged German locale update by cameron5
• Merged Korean locale update by mirpasec
• Merged French locale update by baplar
• Merged Japanese locale update by ginjake
• Merged Swedish locale update by fuzzybipolarbear

Known issues:

[Frooxius]

2025.8.20.580 [PRE-RELEASE]
I squeezed one more bugfix! This should fix dash/facet anchors not loading after syncing on Linux due to... slashes >///>

NOTE: The prerelease uses separate local database due to slight incompatibility between LiteDB with .NET 9 and Mono. You will need to do a fresh login and you'll have a fresh local. I don't recommend using those permanently as the database will be switched back to main location on release.

The goal of these builds is to find bugs and issues and fix them before public release for general use - however since we're very close to release, these are mostly there for general use.

TEST AT YOUR OWN RISK

You can see status of the tasks here: The Splittening (view)

If you'd like to help testing check this post here: #4774

Fixes:

• Ensure Workspace paths using the same slashes on Linux, fixing dash & facets resetting on very launch on Linux (reported by @shadowpanther, issue The Dash's main screen gets reset every launch #5227)

[jvyden]

You can capture some pretty interesting metrics via performance counters since we're on a modern CLR now - .NET just has this stuff built-in and easily readable. I did this in a session with about 14 people, and you can see there's ~53mb of memory being allocated every second, with a GC every few seconds:

You can do this with the dotnet counters tool. I used dotnet counters monitor --name Resonite --showDeltas to call it.

[bredo228]

Tried the prerelease on some old hardware - pretty impressed with how it runs.

Managed to get Kulza's Redwood Mansion Pool map to run at 20fps on a Core 2 Quad Q6600 - considering this is a 18 year old CPU, I'm impressed

[Frooxius]

What does it run like on the normal build?

[keerifox]

initial impressions are good. though for further testing i'd need to wait on v-sync or frame limit to be implemented, as in its current state it places an unnecessary strain on my hardware ( yes i need all those 360 FPS in my Local /j )

[JackTheFoxOtter]

Did a small test this morning, everything went pretty well, stuff loaded super fast, barely any hitches when things were loading. At the end someone tried importing a ResonitePackage and the renderer crashed for everyone. The main process didn't though (which was super funny, since we all crashed to desktop, but we were still talking!). I had to force-close it with the task manager. Notably there Resonite showed up as a background process, which meant it wasn't showing at the top of the list in the task manager. Not sure if that can be tweaked. I'm also not quite sure what to report in an issue for the crash, since I haven't had time to test more / reproduce it, but here's my log files from that session:
J4-C - 2025.7.8.248 - 2025-07-08 07_57_00.log
Player.log

[fulgenscode]

I've also had it crash several times with no window but a Resonite process (without the Resonite icon) running that I had to kill before I could start it again.

[TwinkieShip]

Unable to launch resonite with the prerelease, i hit play and it tries to launch then a few seconds later it goes back to saying play on steam with no log file made at the directory or
DESKTOP-IHUMUJ9 - 2025.7.8.248 - 2025-07-08 23_07_12.log
even the new directory

[TwinkieShip]

removing all launch args that change the data/cache path fixed it.

[Krzeszny]

Similar issue.
On the first try it didn't launch and showed a blank window, but I removed all launch arguments, then launched it, then readded all of them, and then it would load local home.
It crashes when I have -LoadAssembly Libraries/Project-Obsidian.dll in the launch arguments, however, but there's nothing unusual with that.
It loads correctly with custom cache/data paths now but when I load any world that isn't my local home, the renderer crashes.

[JasonMo680]

WOW. Quick test this morning. The Alien Rescue world (not cached) loaded in 2-3 seconds. Shadowed Cove loaded before I could close the dash, so like 1 second. New MetaMovie world loaded in 3 seconds. And I just kept watching my frame rate go.... UP? I've never seen it do that before. Held a steady 120fps in all those worlds. Feels like an absolute winner, game changer, and a true performance update. No performance issues or weirdness that I could see. Had to remove my launch arguments.

[KyuubiYoru]

Going crazy with particles no longer increases the cpu load, is the Particle system no longer multi-threaded?

[BlueTera]

First person view seems to be a bit weird when you can see your snoot and such.

[bdunderscore]

This is expected - RenderTransformOverride/RenderMaterialOverride aren't implemented yet. I'd recommend using third-person cam (F5) to test until those are reimplemented.

[BlueTera]

A reason i'm not going to test further.

[KyuubiYoru]

Nearclip does work as an temporary alternative.

[Krzeszny]

I like seeing my snoot in FPV :)
You can move your POV so that it's only visible at the bottom by moving the head proxy's target.

[alexderpyfox]

2025-07-08.20-47-27.mp4

the vieuwpoint not connected to the model so when jumping or just idle animation it does this where the inside of the head gets visible

[alexderpyfox]

2025-07-09.15-06-42.mp4

this is main branch there is no rtc there either and my nose is still visible as is intended and the head from view stays normal without moving around

[alexderpyfox]

2025-07-09.15-11-31.mp4

and this is the prerelease you can see its something else not rtc that is responsible for keeping the head in place

[alexderpyfox]

so in the prerelease the head is detached

[JackTheFoxOtter]

RenderTransformOverride is simply not implemented yet on the prerelease branch. It's what is responsible for keeping your head steady in first-person view, externally your head is bobbing because of the procedural avatar animations. But the RTO cancels that out in first-person view only. Which isn't implemented yet on the prerelease branch.

[alexderpyfox]

oh i thought it was for nearclip and farclip and removing meshes from vieuw
i got confused

[ModernBalloonie]

Just wanted to say how much better testing is for these builds.

For crashes, I dont have to sit through the insanely long startup process because... well, Resonite starts up so fast now! So testing crashes is so much less annoying.

[FoxoBread]

Trying to launch via Steam on Linux with Proton currently doesn't seem to work.
Running Resonite.exe via Proton also doesn't seem to work.
The furthest I have gotten is running dotnet Resonite.dll in a Proton command prompt, which produces the following error.

Unhandled exception. System.TypeInitializationException: The type initializer for 'System.Management.WmiNetUtilsHelper' threw an exception.
 ---> System.ComponentModel.Win32Exception (126): Failed to load required native library 'C:\windows\Microsoft.NET\Framework64\v4.0.30319\wminet_utils.dll'.
   at System.Management.WmiNetUtilsHelper..cctor()
   --- End of inner exception stack trace ---
   at System.Management.MTAHelper.IsNoContextMTA()
   at System.Management.MTAHelper.CreateInMTA(Type type)
   at System.Management.ManagementPath.CreateWbemPath(String path)
   at System.Management.ManagementPath..ctor(String path)
   at System.Management.ManagementScope..ctor(String path)
   at System.Management.ManagementObjectSearcher..ctor(String scope, String queryString, EnumerationOptions options)
   at Hardware.Info.Windows.HardwareInfoRetrieval.GetOs()
   at Hardware.Info.Windows.HardwareInfoRetrieval..ctor(Nullable`1 enumerationOptionsTimeout)
   at Hardware.Info.HardwareInfo..ctor(Boolean useAsteriskInWMI, Nullable`1 timeoutInWMI)
   at FrooxEngine.SystemInfo..ctor() in D:\Workspace\Everion\FrooxEngine\FrooxEngine\Devices\SystemInfo.cs:line 15
   at Program.<Main>$(String[] args) in D:\Workspace\Everion\FrooxEngine\GraphicalClient\Program.cs:line 29
   at Program.<Main>(String[] args)

OS information: Linux 6.15.5-arch1-1
Proton version: GE_Proton10_8-1
Proton dotnet version: 9.0.6
Proton dotnet information:

.NET SDKs installed:
  9.0.302 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 9.0.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 9.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 9.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 9.0.7 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

[bredo228]

There's an issue tracking this: #4789

[Mrdabup]

I did some simple FPS testing between the current build of Reso and this build. I've noticed an increase in FPS in this build. What I'm most impressed is with the following metrics I took when I was in Redwood. Redwood (with the old renderer) hit 15 FPS on average, with a low 1% of 4 FPS, on the other hand Redwood (with the new renderer) hit 37 FPS on average and a low 1% of 11 FPS. In general I'm impressed how this has gotten so far and I hope this continues in the foreseeable future.

[epicEaston197]

I've noticed that along with the higher FPS it takes a lot more avatars to actually make your FPS dip So even if the FPS is similar between both builds it takes a lot more avatars/users to actually dip your FPS in the pre release

[Krzeszny]

Is it normal for now that all meta memes are broken?
They just don't play.

[uyjulian]

Video playback is NYI.

[KyuubiYoru]

There is a crash upon entering "Bumper Dome" in "MMC: The Metaverse Hotel"

World Link: [MMC: The Metaverse Hotel]

Exception:

16:49:31.082	Exception when running engine update step. Stage: FrameStart
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
   at FrooxEngine.Engine.HandleFinishedReflectionProbes(List`1 probes) in D:\Workspace\Everion\FrooxEngine\FrooxEngine\Engine.cs:line 1428
   at FrooxEngine.Engine.UpdateStep() in D:\Workspace\Everion\FrooxEngine\FrooxEngine\Engine.cs:line 1474
   at FrooxEngine.Engine.RunUpdateLoop() in D:\Workspace\Everion\FrooxEngine\FrooxEngine\Engine.cs:line 1269
16:49:31.084	Unhandled Exception:

System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
   at FrooxEngine.Engine.HandleFinishedReflectionProbes(List`1 probes) in D:\Workspace\Everion\FrooxEngine\FrooxEngine\Engine.cs:line 1428
   at FrooxEngine.Engine.UpdateStep() in D:\Workspace\Everion\FrooxEngine\FrooxEngine\Engine.cs:line 1474
   at FrooxEngine.Engine.RunUpdateLoop() in D:\Workspace\Everion\FrooxEngine\FrooxEngine\Engine.cs:line 1269
   at GraphicalClient.GraphicalClientRunner.UpdateLoop() in D:\Workspace\Everion\FrooxEngine\GraphicalClient\GraphicalClientRunner.cs:line 114

Full Log: [WIN11 - 2025-07-09 Log]

[jae1911]

You might want to open a proper issue for this: https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/new?template=prerelease.yml

[KyuubiYoru]

Its already fixed

[ohzee00]

Running into a issue I wanna get more eyes on and see if anyone else has it too.

I am noticing performance randomly tanking in some world that seems to be tied to two things, Processed Tasks skyrocking suddenly (going from roughly 80 to the thousands) and appearing at the same time, d3d11: RegisterNativeTexture could not get texture repeating in my player.log. During this period crashing seems to be much more likely, however I can't be certain if those two are connected.

This is horribly inconsistent, I restarted three times to see if I can trigger it doing the same actions in the Sandbox and as I started writing this while Resonite was idle on the debug screen, I saw Processed Tasks going up to the thousands and the above texture error repeating in my logs.

Has anyone seen this in their logs/general performance? What were you doing and can you consistently do it? The latter question is what is stopping me from making a issue directly about this.

Example of my log that includes a crash that just happened when I tried exciting the world while the above issue was happening.
Player.log

[ohzee00]

As of 2025.7.15.1402 I can't seem to replicate this issue, namely with processed tasks going into the thousands after roughly a hour of idling, moving around and closing/opening worlds.
I do see d3d11: RegisterNativeTexture could not get texture happening at times but not to the degree that I had before, which that is probably a unrelated issue.

[ultrawidegamer]

Happened to me again in 2025.7.15.1402 here is a crash log
Crash_2025-07-15_235234275.zip

[TisFoolish]

This should be submitted as a bug report instead of as a comment on the discussion, that way it can be tracked properly

[ohzee00]

I am aware, the conditions of these were not something I could easily replicate nor say what the cause is. Especially now that I can't replicate it at all. Unless @ultrawidegamer has a series of steps that led to that crash happening that is semi-consistent.

[ultrawidegamer]

@ohzee00 it seems like it might have just been a lucky fluke... i cant easily reproduce the issue anymore and am testing it some more to see if i cant get something reproducible

[Krzeszny]

Can someone else test if gm_construct also gets stuck on loading for them?

I'm also getting weird lines in the log:

12:50:56 PM.792	PUT request to https://api.resonite.com/sessions timed out. Remaining retries: 7. Elapsed: 121.75s

12:50:57 PM.022	POST request to https://api.resonite.com/assets/40e0aacd5977a9eb353f4fe6443417c9d27fe86a26c06d641353ee757e34c91b/meshVariant/version=2&datatype=MeshCollider&compression=LZ4 timed out. Remaining retries: 7. Elapsed: 121.75s

12:50:57 PM.092	PUT request to https://api.resonite.com/sessions timed out. Remaining retries: 8. Elapsed: 90.75s

12:50:57 PM.123	POST request to https://api.resonite.com/assets/21d8139a100c2868ac1d432b4f19759c39147bc79784f36797d6d9f28143b5a0/meshVariant/version=2&datatype=DualSidedMeshCollider&compression=LZ4 timed out. Remaining retries: 7. Elapsed: 121.75s

12:50:57 PM.574	PUT request to https://api.resonite.com/sessions timed out. Remaining retries: 10. Elapsed: 30.00s

[ohzee00]

Just tested here, seems fine on my end. I would try resyncing your system time and/or see if there is any network issues.

[Krzeszny]

Just tested here, seems fine on my end. I would try resyncing your system time and/or see if there is any network issues.

Dunno, it worked after a Resonite restart so I can't repro.

[alexderpyfox]

DESKTOP-OTQN0RR - 2025.7.30.1026 - 2025-07-30 20_44_36.log
vr crashes on start

[jae1911]

Please open a proper issue about this.

[alexderpyfox]

i dont know how to do that this is the prerelease one and not main

[jae1911]

Use the prerelease bug type: https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/new?template=prerelease.yml

[alexderpyfox]

importing fbx does a crash i looked in the log it doesnt say what caused the crash the log just ends abruptly

[bdunderscore]

Reported at #4803

[kazu0617]

Since this is a performance issue, it may not be appropriate to post it at this time.

In UniFesta2024, the framerate goes up and down considerably compared to the normal version.
Especially after loading the booth.

Probably because of the Uploading related logs (especially the stack trace).
We will measure it when we get a performance update and report any problems.
*On the other hand, the regular version spikes more before loading the booth.

Pre-release

2025-08-05.19-00-37.mp4

FUZZY-2504-WIN - 2025.8.5.477 - 2025-08-05 19_00_00.log

Release

2025-08-05.19-04-25.mp4

FUZZY-2504-WIN - 2025.6.17.855 - 2025-08-05 19_02_40.log

[kazu0617]

I feel a little lighter.

[alexderpyfox]

#4803 can this issue be reopened because its crashing again when importing fbx
edit
it was just one specific model that had the issue which only crashes on prerelease but i exported it differently and now it doesnt crash and other models still work with fbx units scale so not a big deal

[Krzeszny]

Why not open a new issue?

[dragos240]

We're starting the testing with desktop only mode - VR does not work yet - but it will soon! However this is not necessary for initial rounds of testing.

Is this still the case? I see on the issue board "reimplement VR support" is in "done", but there are a few VR related crashes. I'm wanting to test with VR and was looking at the first post because it has the instructions and saw this.

[sylvathemoth]

vr does work, ive been running it in vr mode since vr was announced. fairly stable too.

[dragos240]

I just tested this on Linux, and aside from the visemes not working due to a library not being available on linux, I'm getting smooth, 70 fps in cloud home in VR with Monado with no visible visual hitches. Can confirm it works pretty well.

[Alex-2Pi]

My dashboard was reset during Prerelease testing.
At first, I thought it was only temporary, but today I see that I have also lost all of my private space on the normal version.

[dragos240]

I think that would be a good reason to create a ticket with Resonite staff

[Alex-2Pi]

I thought so too, but I don't have any logs for that.
And I won't be able to point out in which update this specifically happened.

[dragos240]

I still think you should reach out. They might be able to see the event when it happened. It's better than letting all your private inventory space go away.

[Alex-2Pi]

The issue is reported.

[Zyro1331]

I know it's a bit too late, but I'd definitely advise for anyone to use the -NeverSaveDash launch argument when testing prerelease versions of Resonite.
You just never know when a content incompatibility could occur and totally mess up your Userspace items like your Facets and Dashboard.
It has saved me a ton of headache, especially with the Help Tab being absolutely brand new and being incredibly easy to accidentally grab and end up tearing it out of the dashboard prematurely.

[XymaScope]

i have a few issues, not sure how best to report them, have a few logs of the ones i have figured out, and a bunch more idk. i'll include one from the first issue.
evina-eos - 2025.8.13.581 - 2025-08-14 02_16_04.log

System

Linux, Arch (EndeavourOS) a few updates behind, but relatively up to date

Issues

1. Reload Textures button causes crash
2. Volume of the application in KDE cannot be changed from the taskbar (since audio is handled by Awwdio, which is now seperate from Renderite?) can still be changed in audio settings

Reproducing

1a. Go to Settings, Graphics
b. Change Relative Texture Size
c. Reload all textures
d. crasg >w<

2a. See other applications playing audio
b. Taskbar has audio icon, which can click to mute, or be hovered to bring up preview with volume slider
c. Resonite does not have this behavior (it had before Splittening)

[jae1911]

Best way to report issues is through a prerelease bug report: https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/new?template=prerelease.yml

[shny-scott]

I tried running prerelease for the first time today and I quickly ran into severe hand issues. Both LibOVR (Virtual Desktop) and OpenComposite give me a single mangled right hand (using the left hand model??) that cannot navigate menus. SteamVR worked fine, all three of these environments function perfectly on stable.

[shny-scott]

Okay, but Oculus mode is still broken. That's the major issue I'm reporting, I just noticed the same behavior in OC in case that helps for testing/reproduction.

[dragos240]

Have you tried SteamVR mode? My understanding is Oculus mode is a legacy mode. Like, SteamVR mode is just VR mode. Especially on Linux, there's no reason to use Oculus mode.

[shny-scott]

I'm not on Linux. I would like to avoid running SteamVR for the performance impact it has, my machine can handle it in most other games but I want to squeeze every frame I can out of Resonite. While it is true that LibOVR is effectively legacy, it's been replaced by OpenXR which Resonite does not support yet.
SteamVR does work fine, but so should any other OpenVR environment like OpenComposite. Unless any official note is made about the deprecation of LibOVR support in Resonite, I would still expect Oculus mode to work as well. Headset tracking still works, I can see things and open/close my dash, it's not like the code paths have been fully ripped out.

[dragos240]

Oh, I thought OpenComposite/xrizer was a Linux thing. That's where my confusion was. Fair enough.

[shny-scott]

xrizer is a Linux-only thing, it seems. OpenComposite was just a lightweight OpenVR environment for LibOVR headsets that evolved into something that happened to also be useful for Linux users.

[Frooxius]

Just a heads up, given that we had feature parity, resolved major general stability issues and other bugs and there have been a number of sessions and events on the prerelease that ran quite stable, we have locked in release for this Wednesday (20th) to main!

This doesn't mean that work will stop on 20th - there's still a number of minor issues that we'll resolve post release, but we don't see any as blockers for general use - many of them are either very specific scenarios and have workarounds - essentially the builds now feel good for normal use (with many people already migrating to the prerelease) - meaning we can deal with them in release (which makes the process also easier).

Unless something catastrophic comes up, we'll sort out the most pressing remaining issues by 20th and then more in typical post-release iteration!

Thank you everyone for helping us get things to this state so far and catch so many bugs and issues and make the builds as stable as they can be!

[jvyden]

THE SPLITTENING IS NIGH!

[noblereign]

Can you believe it guys? The Splittening, just two days away. The Splittening's in 2 days! Woohoo! I am so happy about this information. Splittening! Just two days away, oh wow. Can you believe it? The Splittening! Just in 2 days! It got here so fast! The Splittening! Just two days away!