Hi Apapappa, I just played the Zordak Demo and I love it! I run the YYC version on a 5 year old potato laptop with a Pentium and Intel HD graphics and it runs smooth, and I didn't found any bugs or issues.
As a possible feedbak, the only thing that I can think of is that it may be good to have a button to stand still while shooting diagonaly. Other than that great job!
I hope you'll have great success with this game!
Hey, thanks for trying the demo and I'm glad you like it. :)
Good to hear it ran smooth as well.
So, there's already two buttons dedicated to aiming up/down diagonally, by default it *should* be the shoulder buttons on controller and A/W on keyboard, otherwise you have to check the control configuration and then you can bind them to whatever you want.
Anyway, thanks again for playing and for the feedback. ^^
Hi Apapappa, sorry I didn't noticed before that there are these buttons for diagonal aiming. I tried again the demo and notice that they don't work by default, only after I went in the controller configuration options.
But, I said before I didn't find any bugs, well I think this might be a bug though. I'm using an Xbox Series X controller (later also tried an Xbox One and a PS4 controller). On both Xbox controllers the shoulder and trigger buttons started working only after I went in the controller configuration menu, even if I didn't change anything. But the left trigger for straight down aim never worked, even when remaping or reseting the controller configuration. Also on the PS4 controller I noticed that several buttons do not mach, for example, cross button is actually circle button, and most buttons had this issue on the PS4 controller. I tried this with only one cotroller plugged in at a time and relaunching the demo each time after swapping controllers. I may try the demo again later on a different PC to see how it goes, in case it has something to do with the PC I'm using. Hope this helps, and have a good day!
Hello again. I just tried the demo on another PC with the same controllers and this time they worked fine, it detected all shoulder buttons by default on both Xbox controllers and also the PS4 controller, with no need of going to the controller configuration. Also left trigger worked correctly when aiming straight down, so I guess it was a problem related to that particular PC. The only remaining issue is that the face buttons for the PS4 controller do not match (triangle, square, cross, circle). Anyway, I love the game, good day!
Hey, so, I don't know why it wouldn't detect the buttons before entering the config menu, never heard about this until now, I'll put it on the list but at this point it pretty unlikely I'll be able to do anything about it.
Not sure what's going on with the "aim straight down" button either, I'll put it on the list.
Regarding controller button names not matching, this issue has been around forever and I *think* there's still a message on the config screen telling you about this.
This issue is not very easy to solve since all controllers use different button IDs for each button, so lets take this imaginary example:
PS4 X Button ID = 0
Xbox A Button ID = 1
Off Brand PS4 Controller X Button ID = 2
Off Brand Xbox Controller A Button ID = 3
As you can see, this poses a big problem if Button ID 0 = X/A Button in the engine, it would now give you a completely different button name for Xbox A Button since it's ID is 1, same for the Off Brand controllers.
And this is why the buttons do not always match (or rather possibly never match) since there is no way for me to know what button I'm dealing with if they all use different IDs.
But as long as the buttons actually work as you bound them then this is somewhat fine, not ideal of course but at least you can play with the bindings you want.
And with all that being said, I'm working on an update to the demo which will be using a newer version of the engine and as such this may or may not be working better now, I can't be sure until it has been tested though, so we'll have to see if this is still around when the updated demo is out.
But yeah, glad to hear it worked better on another PC and thanks for telling me about these issues, as mentioned I'll be putting some of them on the list and try to fix them later. :)
