Big bug to get component from Needle scene

🌵 Needle Engine
1

Hi,

A big bug is appeared after that I only opened my Unity scene.
I’m on the react Setup and, I don’t know why.
After it my component cannot be reached through my scene.

The part of my code in case :

useEffect(()=> {
    if(needle) needle.getContext().then((context) => {
      const nodeScript = GameObject.getComponentInChildren(context.scene, LoadModelsFromNode)

      // console.log(context.scene)
      
      if(nodeScript) {
        // We save the script locally
        setNode({component: nodeScript})
        
        // We add the settings used to load the models
        nodeScript.settings = settings
        
        // We start the loading
        nodeScript.loadAll()
        
        nodeScript.historyPromise.then(() => {
          // And we set the history load from the script
          const actualDate = new Date()
          const structuredDate = actualDate.getDay() + "/" + actualDate.getMonth() + "/" + actualDate.getFullYear()
          const structuredDateYes = (actualDate.getDay()-1) + "/" + actualDate.getMonth() + "/" + actualDate.getFullYear()
          
          // We place the timestamps
          nodeScript.history.map(item => {
            if(item.date == structuredDate) item.timestamp = "Aujourd'hui"
            else if(item.date == structuredDateYes) item.timestamp = "Hier"
            else {item.timestamp = "Précédemment"}
          })
          setHistory(nodeScript.history)
          sendToServer(nodeScript.history)
        })
      }
      
    })
  }, [needle])

I got my context, I got my scene and the Object3D which got the component is in here.

But “nodeScript” is always null, somebody know why ?

Original Post on Discord

by user 224464722878005248

2

Update: I added a random component and save
After I removed it directly and save

And now it’s fixed, but big fear

by user 224464722878005248

3

Sounds a bit like something with caching or component gen wasn’t updated correctly / as you expected
Please let us know if you can reproduce it!

4

In fact when I restart unity, I need to ignore compilation errors.
And when I try to udpate needle it seems to bug :

by user 224464722878005248

5

image.png
image.png2341Ă—836 116 KB

by user 224464722878005248

6

image.png
image.png1482Ă—682 65.4 KB

by user 224464722878005248

7

The top one seem to be from codegen from one of your components?

8

Don’t recommend ignoring compiler errors - they’ll break everything else most likely.

9

image.png
image.png2243Ă—1373 331 KB

by user 224464722878005248

10

The AssemblyResolutionException is a Unity thing; you can disable assembly validation in Player settings
image.png

11

So what’s LoadModelsFromNode.ts containing? And how does the cs file look?

12

image.png
image.png1317Ă—1760 403 KB

by user 224464722878005248

13

It contains all of the code use to load my model in my scene from another server

by user 224464722878005248

14

image.png
image.png1489Ă—787 60.4 KB

by user 224464722878005248

15

I don’t know what’s appends

by user 224464722878005248

16

I don’t see this option :

by user 224464722878005248

17

image.png
image.png990Ă—287 28.4 KB

by user 224464722878005248

18

That is expected (just typical Unity behaviour) when even one script doesn’t compile

19

They should reappear once you fix the error in that script, mind dropping the .cs file here?

20

image.png

by user 224464722878005248