Search results for query: *

Oh it is possible 1.22.0.2 maybe changed something as their were more significant changes there.

I would be very surprised if 1.22.0.3 broken anything since very little was changed. I don't think I changed any of the public methods on any classes. edit: yeah I checked and nothing public facing has changed. You might try a repair in case something was corrupted. Run VaM_Updater.exe, click...

Yeah you can re-enable now. When you disable the option it removes the data folder which includes the cookies, so it effectively clears the cookies when you do that. You should be able to re-enable and use without issue now as the bad data was removed. I suspect a bad cookie was somehow created...

Can you please try the following? Go into the security preferences and turn off the Store data option and then try again? It seems you might have a corrupt cookie that is causing this. I am putting in an error to trap this condition for next release that should also work around the issue, but...

Do you happen to know what Resource you were trying to download here? That might be helpful to root cause, but the output log helps me as I can put in a fix to trap this error, report it, and then move on to next queued item. Something won't get downloaded when this occurs, but at least it won't...

The log is recreated each time you run VaM, so I would need a log file immediately after you experience the issue. The one above does not appear to have what you describe or there was no error when it happened.

I have not been able to replicate this issue. It could be there is some error that is occurring and preventing the queue from processing. The only way I will be able to debug and solve this is if someone could send me their log file when this happens so I can see what it might be. VaM creates...

This feature requires a namespace that would expose VaM to serious security holes when using plugins, so it is not permitted.

I haven't fixed it so parent loops can't be created, but I have fixed it so it will no longer create untrapped errors and cause issues. This will be in upcoming 1.22.0.2 patch release.

I haven't been able to replicate this. I was able to make a Cube atom with preset attached here and you can clearly see it includes the plugin and plugin data. It loads and operates correctly.

storePresetName is a new option to determine if the preset name is stored in the scene or not. There is a checkbox for it on the Preset / Custom tab. The reason this was added was to prevent false dependencies from being put in the scene save file that ultimately did not affect the scene in any...

I just made a test of this and I'm unable to replicate. { "id" : "Trigger", "trigger" : { "displayName" : "A_LoadPresetWithPath", "startActions" : [ { "name" ...

I'm not able to trap anything before a Unity hard crash like that so I can't fix this.

When I added this I decided it was not a good idea to hide the trackers on startup because then you would not be able to know if they were working or not. IMO it would cause more confusion if they were not on by default at startup and then you have to turn them off each time.

I have this fixed in upcoming release. The fix is to make it so that toggle only changes the Atom UID if you are manually loading using the browser. The trigger part is what I fixed. It was not supposed to change atom UID on trigger subscene load from path.

Oh I see - calling a SubScene load with a trigger causes the atom to be renamed. That is a bug. That option was only supposed to affect manual load, not trigger load.

Auto-Set UID is supposed to only be for when you use the "Load Existing..." button and browser. When you have it on it should set the Atom UID to match the SubScene Signature. During normal scene load, the UID should just be set to what is in the scene file itself. You can always manually...

I have this fixed for next patch release (1.22.0.2)

This isn't something I would be able to fix. This is an issue somewhere with graphics driver and/or Oculus Link system.

1.22 added a new user preference where you must enable Leap Motion. Make sure this is checked. The reason this was added is the Leap Motion driver can hang the application if VaM is firewalled and prevented from talking to the Leap process. This was mentioned in the release notes but I know it...