• Hi Guest!

    We are extremely excited to announce the release of our first Beta for VaM2, the next generation of Virt-A-Mate which is currently in development.
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.

For a couple of weeks I get "NullReferenceException: Object reference not set to an instance of an object" on any scene and right on VAM start

w0porn

New member
Joined
Jun 10, 2022
Messages
8
Reactions
1
Hi, I've cleaned up my addon packages around new years eve and everything ran without error. About 2 weeks later I started getting this:

Code:
NullReferenceException: Object reference not set to an instance of an object
at DeleteObsoletePackages.DeleteObsoletePackages/PackageBuilder_InitUI.Patch (MVR.FileManagement.PackageBuilder,UnityEngine.Transform,bool,MVR.Hub.HubBrowse) <0x00029>
at (wrapper dynamic-method) MVR.FileManagement.PackageBuilder.DMD<MVR.FileManagement.PackageBuilder..InitUI> (MVR.FileManagement.PackageBuilder,UnityEngine.Transform,bool) <0x010a1>
at JSONStorable.InitUIAlt () <0x00025>
at MVR.FileManagement.PackageBuilder.Awake () <0x00074>

UnityEngine.Object:Internal_CloneSingle(Object)
UnityEngine.Object:Instantiate(GameObject)
MeshVR.<LoadAssets>c__Iterator0:MoveNext()
UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)
 
(Filename:  Line: -1)

This does not only happen in any scene I load but also at the start of Virtamate itself. Scenes work as expected though. The Exceptions never point to any actual file as far as I could see. I had a look at the output log in %AppData%\LocalLow\MeshedVR\VaM hoping to see deeper into the error but it is just more of the same.

I have since started the updater and checked both core integrity and "check all" but the error spam persists.

Can you tell me what is wrong?
 

Attachments

  • output_log.txt
    34.7 KB · Views: 0
Looking at your log file the most obvious errors are related to Bepinex plugins, so I'd start by checking you have properly updated versions of Bepinex and the plugin, and if it persist you should probably check with Vamplugins if there's some initialization bug that's snuck through.
 
Turns out it still happens when bepinex is removed completely from VAM. Any pointers? Should I start over or try starting without any addonpackages and go trough the 4000 of them?
 
I'm having the same problem. Did a fresh install with no bepinex. No crashes. I installed the performance patch, and loaded a complex scene. And its back to crashing.
My logs are here:
 
Back
Top Bottom