Question Injection on instantiated Scriptable Object from Game Object Context Installer

Hey guys, I'm stuck on something about Zenject/Extenject. Any one has any idea how I can fix that ?

I have Player gameObject with Game Object Context which instantiate Character prefab by factory and Charcater has Game Object Context. In CharacterController which is a facade class on Character I instantiate a few Scriptable Objects in this way:

Code (CSharp):

1. private readonly DiContainer _container;
2.  
3. public ZenjectResourceFactory(DiContainer container)
4. {
5.     _container = container;
6. }
7. public Object Instantiate(Object @object)
8. {
9.     Object instance = Object.Instantiate(@object);
10.     _container.QueueForInject(instance);
11.     return instance;
12. }

In the Character Installer CharacterBehavior and CharacterPowerup are bound by Container.Bind<CharacterBehaviorContext>().AsSingle().NonLazy(); and Container.Bind<CharacterPowerupContext>().AsSingle().NonLazy();

But the issue is CharacterBehavior and CharacterPowerup are not injected into those Scriptable Objects [Inject] methods.

 

If you are creating these instances after the initial install phase, then I believe using DiContainer.Instantiate instead of Object.Instantiate and QueueForInject would work.

 

Thanks for the reply.
Unfortunately it doesn't work either.
Also as I noticed, actually DiContainer.Instantiate is Object.Instantiate + DiContainer.Inject and I think they are totally same things. But again, I've tested that and no success.
From github doc:

 

Did you need to make another thread about this? Mind you it was annoyingly hijacked by the usual suspects.

Was there any attention paid to my suggestion of using plain C# classes? Instantiating scriptable objects is probably work you don't need to do.

 

I made better description for the issue I have, so I made another topic.
Yup, I read your suggestion but it is not related to my problem also my system is based on using Scriptable Objects for different behaviors for different characters and I don't have a plan to change it. Also I've noticed same issue on plain C# classes. Do you have Zenject experience btw ?

 

Yeah looks like it uses DiContainer.Inject internally - which is not DiContainer.QueueForInject. But if that didn't work either, then I guess there must be some other issue here.

 

Yup, I've tested with Inject too. No success either.