Finding an GameObject with mainCamera

Hey all!
I decided to try out visual scripting and I was wondering (I googled the heck out of this and didn't find anything) what nodes one would use to return the information of an object at the center view of the camera.

I tried raycast hits, and the best I could pull was vector information.

Any help would be appreciated. I've been fighting it for a couple of hours now.

Thanks!
D

 

I *might* have made some progress.

 

Okay, so it looks to be working, however it seems it's not focused on the center target. I'll futz with that, but if anyone has ideas, I'd def appreciate it.

 

Alright, so it's a bit of a pain because I can't pull much information about the object itself, such as the Label or Tag info.
I'm wondering if I'm butting my head up against a wall using cinemamachine as well?

 

I think I sussed it out. Let me know if there's a cleaner way to do this.

 

Side note: I hate you, `while` loop.

 

Raycast will only return true on objects that have the ridged body component attached. so you could use a spherecast instead to detect any object.

But I think you're looking for Game Object Get Game Object from the collider hit as shown below.

 

Thanks! I did end up getting the game object, but now it looks like maybe I can't use the equals value twice?
See below how during runtime, if the state changes, you can see it's not changed on both connections. This feels like a bug as I'm effectively pulling one value into two different methods. Why would that get sticky?

 

Well here, you are attempting to take the mesh renderer component from the back of the set variable node.

you would have to set the variable than get it again with a seperate node. and also don't need to reference the component directly only the game object. just keep at it and it'll click.


here i use the find object node to get a reference of the game object that can be fetched later on down the line without needing to declare a var. if you're doing instanced prefabs then you'll want to use Transform Child Index. apparently it's faster too.

but you can see the mesh renderer is directly referencing a game object not a component.

does this help at all?

 

It absolutely does! Thank you!

D

 

The diff it appears to me is that I don't need to find an object on start (although I could use this to find the player instead of declaring a var for it), as I am dynamically determining if an object is between the player and the camera.
If there is, it stores the object in a var, disables the mesh renderer and when the object is no longer in the way, it will re-enable the mesh renderer.

Eventually, I'll figure out how to make it so the object goes transparent (which I think I need to dig into material or shader editing for making those calls), but for now, this is very helpful.

Thanks again,
D

 

Sorry, i cant provide anything to the discussion but I'm curious is the mesh render thing a performance thing?
Do you do it to unload things not on screen and if so are there any threads going true on how it works ?

 

good stuff. yeah just takes some farting around with. needs more documentation or more details on the nodes themselves.

 

It's a mid-hack until I get the code sorted. Eventually I'll have it tell the material/ shader to go transparent. It's so I can see the player behind objects while moving them around.
I work in Infrastructure/product/software development, but not in C#, so whenever I get time to come back to my project, I've already forgotten half the stuff I've learned. Lol!

This is me struggle-bussing through it.

That was the first thing I noticed is that the descriptions for all the classes seems extremely minimal.

Thanks again for your help, I appreciate it!
D