LDA #HUD_ELEMENT_3
STA HUD_updateScore
TheNew8bitHeroes said:Sure. My *guess* is that the hud element number doesn't line up right.
For instance, if you use HUD Element 3 as the one that shows the variable score, you need to go to Routines\InitializationScripts\InitLoads.asm and update the part that says ///SET UP HUD HOOKS HERE.
You want to make sure that, in that instance, it says
Code:LDA #HUD_ELEMENT_3 STA HUD_updateScore
This works in conjunction with the GLOBAL_Player1_Score variable, which you should set up as the thing displaying, and the variable being changed.
Lastly, make sure NO OTHER hook is set to update to that element, or it could be overwriting the update.
;;;;;; SET UP HUD HOOKS HERE:
;; what number element does it use?
;; Set your created hud variable to #HUD_ELEMENT_x
LDA #HUD_ELEMENT_2
STA HUD_updateHealth
LDA #HUD_ELEMENT_4
STA HUD_updateScore
LDA #HUD_ELEMENT_6
STA HUD_updateLives
;;;;;;;;;;;;;
TheNew8bitHeroes said:Hm. First boot may be able to be fixed...there is a code HandleScreenLoadHudDraw. Try ORing in the HUD_updateScore - but it should already be there. You should be able to look at it and see exactly what I mean. That SHOULD update it upon loading a screen.
I'm confused about what you're asking above. Are you TRYING to show Element 2 and it's not working, or are you trying NOT to use a health variable? Either way, it should not be a culprit. Though if you don't intend to use it, try commending out ORA HUD_updateHealth in the code I just mentioned...but it shouldn't have anything to do with it.
So the VARIABLE amount of score is loaded into element 4, then? It seems like the variable is working, but not real time update (these are handled separately...you can easily change graphic data when changing screens, but real time updates mid frame are much harder, which is why they're handled separately...the former can happen in line at the time you want it to, the latter can happen ANY time throughout gameplay, so it ends up getting cued and waiting for the next available update frame).
Again, this is hard for me to tech beyond what's shown in the tutorial. The reason I think it has to do with the STA HUD_updateScore or something related is because the variable IS being affected, it's just not showing, and that's the piece of code that determines which of the hud elements needs the update.
TheNew8bitHeroes said:Excellent! Yeah, we're working on a front end solution for this in the hud designer / variable creator that does all this automatically. It's the most sophisticated, nonsensical piece of the engine thus far, but it's cool how versatile it is!
Agree with you! <3loving the tool so far, tons of potential and the support for a beta has been amazing
Rob Burrito said:awesome dale! yeah i'm gonna try to go through from memory and make something playable next. agreed the crew is doing a great job on the tool, just reporting and isolating the issues as much as possible to help debug, and post for solutions for other folks who may run into the same issues while working through the tutorials. it's what we paid to be able to do! i do fully test every bug i find, and bigger ones i typically will try from a scratch build and run through as many variables as i can to give as detailed report as possible. apologies if any bug reports seem informal. try running a restaurant sometime and see how error report levels of logic and courtesy are handled by the public lol. joe seems to be off easy so far with just folks telling him how to run a business ('the way you're doing it is stupid' ...it's endless) and eating bags of dicks is public insult 101 (especially for online comments, a direct message was generous!) i think mihoshi shared the sentiment of rather find and work through this with a small group that understand there will be bugs, vs after release, answering the same thing endlessly, or all the headaches that come with releasing patches to folks who choose not to read the directions haha. loving the tool so far, tons of potential and the support for a beta has been amazing.