How to extend your VRChat Avatar memory to infinity with this simple automatic OSC app (Based !)
Vložit
- čas přidán 2. 06. 2023
- Get the Parameter Sync System here : fuuujin.gumroad.com/l/OSCPara...
If this video helped you, consider supporting me on KoFi : ko-fi.com/fuuujin
Check out my Gumroad : tinyurl.com/FuuujinGumroad
Booth : fuuujin.booth.pm/
Linktr.ee : linktr.ee/fuuujin
Join my Discord server: / discord
What does this system do ?
It uses only 2 ints and 2 floats in the avatar global synced parameters, to store up and sync up to 255 more float values on your avatar. This allows you to use more than the 256 memory allowed for you to use by VRChat.
This allows you to extend your parameter memory for more radials and other uses of floats.
If you are bit of a programmer, you can add even more ints, you can theoretically extend to even more than 255 float values, but I don't think anybody would need that much. Or would they ?
How does this work ?
Unity Magic (see the video for explanation)
What are the uses for this system ?
- Regular radials used to control shader options - Hue Shifts, Emission Strength, Brightness, and others in Poiyomi 8 and other shaders. This can save lot of avatar parameters on your avatar.
- Sending values you need to calculate in OSC and then send onto your avatar
- This is especially good if you want to send lot of data onto your avatar from OSC, but it does not have to be updated all the time. Using this system, you can save lot of avatar memory for different functions that cannot be done using this system.
How many parameters do I need for this module ?
2 Ints, 2 Floats
Is it difficult to use ?
Not at all. The Unity Package has only two files !
Also see the video below for a video tutorial how to install this system.
Instructions
- Install according to the video tutorial.
- Keep the OSC EXE file and .CSV file in the same folder !
- Upload your avatar, run the OSC file.
- The OSC file needs to be running in the background when you are using your avatar.
What is included
- Unity package with all the needed files - FX Layer and Avatar Parameters
- Ready to use OSC EXE app you click and run
- .CSV file to store all youravatar float values automatically, so the system remembers them
- Python source code .py file, if you wish to see and edit the code to fit your needs even more
- Video tutorial how to install and modify - Hry
Thanks bro, you really saved my life
I have an animation controller where I use a combination of two int parameters for id and another int for value. How difficulty would it be to modify this system to use that?
EDIT: Managed to get it to work on my own. Answer to the above question: not that hard if you don't include the trial and error. Managed to make it work with my existing animation controllers instead of having to remake them as shown in the video. Only thing I had to change in my controllers were the transition durations as they needed to be shorter for the controller to keep up with the sync system
i cant use it it says i am at 250 and the OSCPPARAMETERS add 30 so i dont know what do to
what is the purpose of merging animators or layers?
I made it most of the way through, but when changing the controllers, your parameters/controllers didn't show up. The option wasn't present and now I'm stuck.
Hi! I had some success with your tutorial, however For some of the float toggles they dont save properly. For example, the hair hue radial saves and works consistently, but the eye hue radial doesnt save when switching worlds. The body hue radial doesnt work at all half the time. Any suggestions?
You need to have the OSC app running. It saves into a CSV file and the it loads it onto the avatar back all the time, so when you change worlds it will load all the saved parameters back onto the avatar.
If you have the OSC app running there must be some kind of mistake in the setup.
Would there be a way to automate it with VRCFury to have it automatically replace parameters added by VRCF packages with ones generated by OSC Parameter sync?
Since editing VRCF prefabs to make them work with this seems kinda meh and it would also make it a lot more accessible I think.
I have bad experience with VRCFury and do not use it. It ruined 3 projects for me and caused issuses that couldn't have been solved. So I do not plan any interaction with it currently.
@@fuuujinvrc6868 oh ok that's pretty understandable yeah, well guess unpacking and doing it manually it is then. Thanks for the answer tho!
@@fuuujinvrc6868 skill issue
If I use this on multiple different avatars, then switch avatars in game while the OSC app is running, will that throw it off?
I think it would. Basically all your Avis would be locked to the same values. Their parameter values would get overridden by whatever is currently in the CSV file.
One way to avoid that is to use different ranges on your different Avis to prevent conflicts. For example, Avi #1 would have IDs 1 to 40 (for a total of 40 parameters max), Avi #2 would have from 41 to 80, etc... Up to the maximum of 250.
Another, less straightforward option would be to stop the app and manually replace the CSV file with the one corresponding to the Avi you intend to swap to, swap to the Avi, then restart the app.
After merging, can I still use my own fx controller or do I still have to use the one that came with it?
The purpose or meging is to add the original controller to yours. So you can use the one that has your stuff + my system's stuff
@@fuuujinvrc6868 so all I got to do is merge your fx to mine and that’s all?
I picked this up and it does look amazing for specific use cases. However, I'm running into an issue because several of the floats I need to save space on are actually Two-Axis puppets with X - Y values. I can only assign a single integer for Received ID, but it needs to control two floats. Unless I'm misunderstanding something, this can only be used to save space on floats that are used independently, on radial puppet menus. I'd be very happy to be wrong.
I never used this for 2D puppets, so I have no clue tbh
@@fuuujinvrc6868 Ah, understood - in this case it's for positioning of body parts (wings, tail, etc.) Technically possible to reroute to single radial menus for each axis, but a lot less intuitive. I'm not really familiar with how OSC works. Do you think it would be possible for this to store two float values for a given ID and to load both?
its so quiet
Hi this would be awesome but when running the osc script in the background it doesnt seem to be receiving or sending any data to vrc, and seems to be shutting itself down after like 5 minutes (asks me to press any buttor to end).
I should add that i tried both running the app after and before running vrc, disabled firewall and other osc programs i used worked normally.
so far i am relying on the "v1.2" idea of the program, but i noticed the inconsistency.
Any idea what could be the issue the app is not connected to the vrc?
Weird, I know about some people who use the app currently without problems.
Upload the avatar on a new ID, reset OSC once, might fix the problem of the avatra not receiving parameters from the OSC app
does this work for bools and ints as well?