Scene-less Nodes/TransformNodes

Feature requests
,
1

I’m working on a project and need a TransformNode but don’t have a scene since scenes (which are worlds/saves in said project) are generated dynamically. Except for one issue: Node requires a scene, so it throws an error from the highlighted line:
image

From an engine perspective, do we need to have a scene with Nodes? There isn’t any geometry, though it could change some behavior (e.g. the getScene() method).

We can have the scene parameter in the constructor be optional and have another method for setting a scene.

2
3

Hm…

https://dev.azure.com/babylonjs/243fb099-542d-4655-b246-4dfd67131bd4/_apis/build/builds/22287/logs/16
The build fails with a ton of null errors - which makes since. Maybe instead we could have a default scene created with engine instantiation?

cc @GeneralQuestions

1 Like
4

I commented on the PR but I really do not think we should do this change :frowning:

In your project why not creating a dummy scene with NullEngine ?

1 Like
5

Thanks @sebavan!

The reason I needed a no-scene node was for creating default playerData in the project…

Instead of rewriting the engine, it would make more sense to simply code the project not to need default data, which I’ve been trying to remove anyway…

1 Like
6

Could you use the dummy to create the TransformNode then:

delete tNode._scene;
delete tNode.unique;

? Seems like you end up with the exact same object.