distance vs time scatter plot physics drop block

#DISTANCE VS TIME SCATTER PLOT PHYSICS DROP BLOCK CODE#

Simple tests appear to return ID values in the expected range ( e.g. It seems to work correctly returning the ID's for any object, but its not been extensively tested.

#DISTANCE VS TIME SCATTER PLOT PHYSICS DROP BLOCK CODE#

Its a proof-of-concept, so its not pretty and the code as well as the design could be improved. So out of curiosity, I've created a project that uses rendering the objects to a RenderTexture and colors as a unique ID. Maybe someone else has experience of doing this can chime in. I guess worse case a computeShader could work, but that seems a bit overkill. That isn't something i've had to do and i'm unsure if Unity's readPixel can deal with those. The final problem to solve then would be the read back of the color value for the pixel from a non-RGBA32 format. Pretty sure a R32Float would suffice though, but i'd double check the renderTexture formats to see if there is anything more suitable. If you are rendering millions of nodes then that wont work. Now i've used this process in the past but I think I was limited to either 255 or 65535 objects meaning I could use a simple 8 bit or 16 bit renderTexture. Also you probably only want to render to the renderTexture on a mouseDown, no point rendering it every frame waiting for a mouse click. Obviously rendering the instances twice is going to drop performance, though a custom shader for the renderTexture that is bare minimum will help here ( i.e surface shader would be overkill). Once the ID is known you can then do whatever you need to the node back in your main code. Then all you need to do is a screen pixel lookup of the color in the renderTexture to get its 'ID'. detect mouse hits), since a physics or maths based system will generally struggle or require considerable effort to make it run efficiently.īasically you'd render the scene again into a renderTexture and assign every instance a unique color value, or better yet just use the instance_ID value as a color. Frame rate drop off has been more or less linear with the number of points.Ĭlick to expand.Not sure if you are still following this, but for either geometry shader version or once you get DrawMeshInstanced or DrawMeshInstancedDirect working i'd recommend an alternative to raycasting for purely 'selection' based detection ( i.e. This example draws 3.7M points at frame rates consistently above 60 FPS. (Only graphics people who notice the lighting doesn't change figure it out.) Since, it's symmetrical, most people don't detect that it's turning and is really 2D. The best performance I've gotten has been to create 2D billboards that face the camera and are textured to look 3D. I'd like to come up with a way to model and import 3D icons and draw them in a similar way. (Data is sorted into meshes that draw using the same material.) I then use a shader to render the point as a 3D object (cubes or whatever shape you can insert into the pipeline programmatically. I create a point topology mesh at run time representing each data point. I cobbled together an example using geometry shader examples from the web.

It's been a while, but I remember it being a good solution up to maybe 200K points.

I did some experimentation with the particle system. Do you happen to have an example that illustrates your suggestion?

Distance vs time scatter plot physics drop block