Greetings! I know basics of save/load but I want to simplify my life (as we all) 
I can save whole actor to SaveGame, but how I can spawn actor from SaveGame as a whole piece, without iterating through each actor variable?
1 Like
If youâre doing it with the save game, you have to save everything yourself, and load it all back in again.
If you want to be able to just say âsave this actor with all its settingsâ, then youâll need a plugin, like
or
Thnx! Im using RAMA now. Its good but it behave weird
RAMA is OK to save array of references but is NOT OK to save reference as a single variable.
Ive asked this questions in plugin discussion and on store page. Waiting for an answer.
And I dont know C++ to use Savior
Iâve never used RAMA, but Iâm pretty sure it can save single variables in actors
Also, Savior is also exposed to blueprints.
You could be having a problem, because saving references is just not a good idea.
A reference is a dynamic variable, the value could very well not be the same the next time you run the game.
About RAMA I ment it saves âarray of referencesâ variables. But It refuses to save âsingle referenceâ variable.
If that so I will try it
1 Like
Like I say, donât save references. It probably wonât work with any other save plugin.
Can you give an example of when you would save a reference?
Saving references is the main reason to use any plugin at first the place
I mean I can save variables but I need to save reference on objects inside save.
For example in my project I build space ships block by block. And each block hold references to all connected blocks.
So I need to store this ship. Ship holds references on own components only, meaning it is possible to incapsulate references inside save.
1 Like
Thatâs what I thought. I think your problem is saving references, not the RAMA plugin.
If block type A has block type B attached, it can remember the class of the attached block.
If you canât work with class, then working with actor tags is another method. Remember the tag of the attached actor.
Using references will not work in the long run, especially when you package, I suspect.
RAMA saves entire actor so thats good for me.
I may kinda found work around with references - I want to generate my own GUIDs for every object and then restore references by this GUIDs.
Do you think this is feasible way?
That might work, depending on how you do it
I already did this for references that RAMA refuse to save:
If GUID invalid (new object, not from save) - Assign GUID as variable that RAMA can save with object
Then in objects that hold reference Im saving not only reference but also GUID
And on the load I restore reference by GUID:
Ok, that looks pretty good
Are you saying it wonât save these GIDs?
It will
What I ment is - I wanna pay money to plugin developer to do this for me )))))
I dont want to store GUIDs. I dont need them. They are only for save/load
1 Like
It doesnât matter which plugin you use, saving actor references will never work, because they are generated at runtime
You are wrong )))
I will make video a show you how this work in RAMA (but in a strange way)
1 Like
Donât worry about it
It does work - sometimes - , but you canât rely on it.
You can take a look around the forums, people ask this question ( why canât I save actor refs ) about once a month.
Many different people have answered the same thing. Donât save references
1 Like
Ok, Understood
Crap )))
I just checked. Its not RAMA that save references⌠Its my block spawn and snapping logic.
Blocks start to snap to each other the moment blocks appears in the world
So, as you sad. There is no reference save in RAMA.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.