So I’m trying to track down a specific “print string” action in one of my blueprints, and I get lots of results when I type in “print” into the find results bar. However I can’t seem to find a way to actually look up the result in the actual graph? Is there a hotkey or anything I haven’t been able to find? This is really stressing me out, as I’m wasting lots of time just searching by eye through the entire blueprint.
Thanks
Print is very bad way to debug blueprint code, exactly because of problem you have now. Look how visual debugger works (its great compared to prints), and its easy enough to learn it in hour or so just by playing with. So remake all print nodes as visual debugger nodes. I tried to remedy your problem with making custom debug_print node, but its never as easy to use as visual debugger.
There could be a way if function could get actor name and class of object it was called from. Then you could do custom print function that gives information where it was called from. But that functionality is already in visual debugger.
Thank for the tip Nawrot!
Another thing worth mentioning: If you open your Output log (window -> developer -> output log) you’ll see your Print to Screen nodes being printed here but with an extra information: the Blueprint where the print string node is.
Thanks for the replies. However I’m not sure I really have my question answered. Here’s a picture of what I have in mind: http://i.imgur.com/lkFDxEo.jpg
Also on a different note. Does strings simply not work with packaged versions or what? This thing is bugging out on me after package.
