วีดีโอ

Good note! I don't have easy access to a Mac for testing so I appreciate the heads up on this.

Double check the script, it should be parent().par.Numchars which should end up as an integer assuming you created the parent parameters correctly. If you're still having issues please reference the point in the video where you're having trouble (in case I misunderstood where the error is occurring.)

@@polyhop the point is i executed the whole thing , and I achieved the same result as well. But that error is still there , is there any other socials where I can share you the screenshot? Or anywhere, where I can contact you.? Maybe it's my system thing but I'll share with you the exact problem.. even though your tutorial actually worked . I achieved the desired result

@@Shirokokun Strange. And you're using TD version 2023.11340? I don't see any issues when I load the project file in the newest version at least. Are you on a Mac? As far as sharing the result, you can find me on Discord. I'm in the TouchDesigner Discord group for instance, same handle, or through my Patreon (though that is paywalled.)

Check the resolution of all your instancing TOPs (middle mouse button on an OP tells you the resolution quickly.) They all need to be the same resolution or you will see this error. It's possible that the remap TOP needs to be set to use the UV for the resolution for instance.

This sounds like the pixel format might be 8-bit, which doesn't allow negative values. That might explain why it is only working in one direction. You can middle mouse button on a TOP to check what the pixel format is. It should be 32-bit float, which should be set on the TOP at the start of a given chain on the common page. If that doesn't work I'd suggest making sure you are using the same TD version as listed in the description, and double checking that you're following every step in the video tutorial. You can also find project examples through my Patreon in case you want to reference a working example directly.

@@polyhop thanks for the quick answer. I will go with Patreon, thanks!

I don't have a mac to test on unfortunately, though I did pass along the final project to friends with a Mac M3 and it ran correctly on their end. Is there a specific point in the tutorial where the crash occurs?

@@polyhop it crash when we start to run (save) the script.

@@encikazmulfadhlibinkamaruz9360 Is this at a specific point in the video? I'd suggest seeing if you can work your way through the shader, trying to get pieces of it work to sort out the error. Unfortunately beyond that suggestion it will be hard for me to assist without being able to replicate the problem on my end.

I am able to open this without error in both 2023.11340 and the current build (2023.12000.) You can always rename a file CrashAutoSave.toe to access it in safe mode. Then you could do things like reduce the size of the grid / render resolution, which could cause more GPU usage, or disable components so you can turn them on one at a time outside of safe mode to see what is causing the crash. See docs.derivative.ca/Troubleshooting_in_TouchDesigner for more on that process.

Yeah, you use the color section on the 2nd instancing page. Point a TOP with the same dimensions and you can color using RGB channels. Use mono noise + lookup TOP to define a color palette. You can adjust the material to have a constant value (a value of gray) if you want your color to show up directly

@@polyhop Thanks!

This could happen if the number of samples in each CHOP is different (middle mouse to see how many samples.) Make sure the 'grid1' rows and columns, and the noise1 resolution match, and that you've set "full image" for the 'topto1' crop parameter.

@@polyhopthank you it worked!

TouchDesigner 2023.11880

@@MoonLeng-y4o when following the tutorial at what point does it not work in the same way?

Okay after some trial and error I think I found a solution myself and will leave it here just in case someone else runs into the same problem: In the Math that combines the two CHOPs I had to set the Align in the OP tab from automatic to stretch to min/max. Now this does the trick but it somehow screws up the beginning and end of ty so that there is a disconnect in the loop. Putting a filter after the math with the widths around 1 closed the gap in my case. There is probably a better way to fix this but at least it works now :)

This wouldn't be an easy system to do this with. I'm sure it could be possible but would require a much longer video and the result would be something else entirely.

Agree. The switch in feedback is sweet!

You can toggle off the render flag (purple dot on the GEO Comp) if it's still showing up in your render. Unless I'm misunderstanding the question.

with the viewer active in that node, you have to press "W" to turn wireframe mode on

@@polyhopactually when I'm also changing the torange in math to (parent.par.Gridres-1) it's just showing one solid rectangle. But the moment I keep it without -1 , it's showing 5x5 boxes in grid but I also have a Problem , i.e the rectangles in grid is solid unlike yours which is just outlined rectangles. can you help with it? ill continue with the tutorial as for now with this set up only , I'll update if that caused any problems in output. but is possible let me know whats the difference

@@Shirokokun Removing the -1 will show you a "grid" because you're adding a small amount of space between your squares. I imagine the solid rectangle is because you need to point a wireframe material at the grid. If you don't see the wireframe, try moving it forward in the z axis as when both are placed at 0 you can get what is called "z fighting" (I missed covering this in the tutorial, but it's an important fix for something that has inconsistent behavior.) Either way, you should be able to get a similar final result.

I use this "OpenGL Shading Language (GLSL)" package that adds GLSL syntax highlighting packagecontrol.io/packages/OpenGL%20Shading%20Language%20%28GLSL%29 There are instructions through that link for how to add it using package control, so you can do it entirely withing sublime text.

@@polyhop awesome, thank you

Noted! I don't have easy access to a Mac for testing, but I will solicit feedback from some friends with them in case there's a solution to this crash. I like to make things work cross-platform as much as possible.

yes my m1 crashed as well here is the error: Vulkan Device Error The graphics driver has returned a fatal error and TouchDesigner must exit.

@@mamadmadcap Thanks for the note. I sent the example files to a friend with an M1 Mac to test who didn't have an issue. I wonder if there's a point in following the process where it crashes. Do you know where you were in the tutorial when it gives you the error?

​@@polyhop Hey Sorry for the late reply. The crash on my side happend always around the 25 min mark. So everytime the glsl code would be able to execute. But lately I had quite a Vulcan Device Error when writing more involved glsl logic in TD.

Strange! There aren't UI preferences that would let you change the color. As far as I know the way it looks in my tutorial is the way it should look. Could be worth taking a screenshot to the TouchDesigner forum!