Caught that amazing bit of info regarding the back up just a touch too late to do anything with it. Swapped the files over first thing this morning though and everything works again. This coming on the heels of a bunch of finger wagging from my friends that I need to get a some sort of source safe set up, well they can SUCK IT! But seriously I need some kind of off site source safe for reals.
Thanks for the tip .
Ok, for the other post regarding the OOP break down, most of that all makes perfect sense. Classes start as the broadest possible concept, and each related category subgroup inherits their abilities and adds on their own touches, with divisions between them occurring as more and more individuality is noted. I’ll be sure to main line those videos as soon as I can.
I’m not entirely sure I’m following the difference between a CPU tick and a World Tick. Why would the tick of your level be different from the CPU?
For your question regarding a reference variable, I think I might be describing that wrong, but having an object selected in the view port and then right clicking in the blueprint will bring up a context sensitive option to reference it. Good for calling a camera or object to plug into a target pin. Now that I’m really considering it, that doesn’t really sound like a variable as such, at least not in the way that a class would need to be referred to. I promise I’ll do it right in the updated version.
On that note, I have a day off so lets get all that implemented!