what is the purple node stands for?
I keep getting it..
thank you
thanks @joreg
when I copy-paste the whole patch from the Help Browser “how to use Emission Stage” on my own patch, the same happens.
But it does not happen in the helppatch
is there something I did not do in my own patch?
it throws a NullReferenceException… I don’t really know how to debug..??
As a small rule of thumb: “Object Reference not set to an instance of an object” is basically nerdy talk for “something is missing”. It usually happens when you have not connected something that is essential.
Especially if you have set “Pause on error” it will halt the program and jump to the error.
You can press F5 to continue, but most likely it will just stop at the same place. You can keep it paused till you have checked everything that is needed is connected and then continue.
It takes a while to get used to this, but coding is basically 90% finding out how something works and then debugging.
Happy patching!
@seltzdesign thanks for your answer
Yup, I understand the concept of patching, and then debugging.
But when I copy-paste the entire patch from the helppatch, I naively think it would just work!
and at this stage, I don’t know what is missing!
you’ll have to tell us a bit more what you’re exactly doing. what are you copying from where?
I am trying to copy from helppatch for example, from the Probablity Emitter Help Patch
and paste it just to a blank page of my own, so that I can customize and play around to tweak here are there.
I get pink node either in ComputeSystem Node, or EmissionStage Node, or Simulation Node
I first get a pink Node in the copied ComputeSystem Node. I then replace it with a new one with the same values etc and rewire it. Then the new ComputeSystem node works, but Emission Stage Node becomes pink. Then same process, I replace it with a new Emission Stage node, it becomes gray, and then Simulation stage becomes pink. So I fix this one. They end up all gray, but the console keeps throwing me an error
And then when I check again, Compute System is pink again…
When I put them separately in Try Surroundings, they all seem to be okay…
ok, so in this example you describe the issue is that on paste, the constructor of the patch is not called. ie pressing F9 to restart the patch fixes this on my end.
there is the above node that is only executed/initialized on Create. so after paste you have to restart the patch once, to init this node.
1 Like
Ahhhhhh! yes, F9 did the trick.
ok, I will remember that I have to restart the patch after a copy/paste!
thank you!
not generally, but if the paste included a Create (white) operation.
One question though - doesn’t a node also call its own Create operation when created from the node browser, and if yes, should that also be the case when pasted into a patch?
That is the case, the problem is the buffer resource being assigned on create of the hosting patch.