You should post a basic c3p file so it will be easier to help.

But it sounds like you should be using the bullet stepping feature.

https://www.construct.net/gb/make-games ... nce/bullet

Guys

Im trying to implement full screen on joypad button press but not getting it

For me fullscreen wont work on joypad button press

(xbox controller) (on chrome browser / not tried nwjs)

is this a thing ????

So i looked into it a bit more

it looks like browsers have to use the web standard Gamepad API.

Gamepad api default mapping is standard xinput mapping.

However the Gamepad API has the funcionality to recognise different controller types from different manufacurers throuh a controller ID and automatically remap them to a "Standard" (xinput slyle) mapping. But the browser developers have to make the effort to include this with a list of controller IDs.

It seems firefox keeps a list of popular direct input joypad ids and automatically remaps them to standard. Where as chrome possibly dosent and just goes with standard or it dosent recognise your joypad id.

https://w3c.github.io/gamepad/

https://developer.mozilla.org/en-US/doc ... amepad_API

i was reading on steam forums they have same issues because rumble pad 2 is pretty old and uses outmoded direct input api rather than modern standard x input api. i assume that xinput is default expectation for construct joypad plug in. for gamers to use these older pads they have to use bridging software called x360ce

https://www.pcgamer.com/how-to-use-old- ... put-games/

edit i was also reading that htm5 accepts both dinput and xinput so you should get readings using raw data. however you would have to manage compatibility.

its funny though that firefox can figure it out and not chrome.

looks like joypads are a bit of a minefield

Try a few different numbers for the y axis ... eg dual shock has a 5 for the right y axis if I remember.

are you using windows/xbox controller ?

I have dual analog working perfectly for windows/xbox controller but I am using raw data (you cant use the built in dead-zone and other features using raw but I hope to include compatibility with dual shock and other in future so setting up with raw instead)

for example right joy pad weapon angle code as below.

(this bit is just checking a deadzone)

+ System: distance(0,0,Gamepad.RawAxis(0, 2),Gamepad.RawAxis(0, 3)) = JOY_RIGHT_DEADZONE

(and this bit set angle)

-> System: Set WEAPON_ANGLE to angle(0,0,Gamepad.RawAxis(0, 2),Gamepad.RawAxis(0, 3))

( edit ) just to note that if you are not using xbox or windows/xbox controller then the button and axis numbers can be different you have to play around to find the numbers

OK man I can see you are making a infinite runner with random platforms but there are a lot of issues with your events

for a start you are calling F1 from inside itself, which you can do at a more advanced level, but this is not what you want to do here

you need to at least call it once from outside

so move

platforms x < 128 call "F1" outside the function

however this causes another issue that as long as platforms x less than 128 it will keep calling the function to make more map every tick for ever as platforms x is gone off screen for ever.

you could set platforms x back to 0 or whatever it was at the start but you have just created more platforms with the F1 function so now the old and new platforms will overlap

so.... yea. i dont no how to make infinite runner but there are lots of template and examples here and on youtube and possibly in your C2 examples folder. Have a look at those for ideas.

You need to make a variable called "Letter_Number" or something

then add 1 to the variable every time button is pressed

then have event when Letter_Number greater than 3 make Letter_Number = 1

then when

Letter_Number = 1 make text "A"

Letter_Number = 2 make text "B"

Letter_Number = 3 make text "C"

you really need to give us a capx c3p but

1) you have x less than 128 will keep calling gen map not more than 128

2) i dont see x being set or added to anywhere

john Cutter yea i had an identical issue with my game when loading big arrays.

i figured that probably because the first function dosent finish before the tick cycle the second function just gets forgotten. im not sure if right but as Asmodean said it was easily solved with a Boolean true on completion and just use that as the trigger for the debug message or the next function.

Wow, brilliant game brilliant graphics.

Plays fine on my Moto G4 which is a pretty crap phone by all accounts.

I was thinking you should really implement a swipe to go forward as well as the tap and you should also allow a tap left third right third screen to go left right as well as the swipe RL. This would cover all intuitive actions. Also sometimes my swipe registered as a tap to go forward killing me. Also sometimes there appears ton of difficult traffic where previously at the same point it wasn't so bad not sure if that's deliberate

anyway , yes

horribly addictive and inspiring.

Nice one.

So.. the sun finally came out here in the UK after another never-ending winter..

..So Im feeling positive and am positing a vid. This is where I am at...

Ive gone back to a pixel art style. changed the aspect ratio slightly so its a bit higher. will I stick with it?... I dont know. Also trying to make this 3D scaling work, just about got it but all the waypoints Ive put in by hand on the constuct 3 array editors just to test so still need to build that functionality into my editor so I can make a lot of them quickly for the game. Other than that Im trying to put the lives system in , the menu system in and level change and reset ect. The usual things in a game that you never think about but they sure are PITA to get right. Cos Im such a damn noob and this game is essentially just continually building on "my first game" I never used different layouts to for different levels. Im thinking this is going to be a bit of an issue going forward but we'll see. Also the framerate tanks when a lot of enemies overlap so that will need to be sorted. Oh yea and there is a really annoying bug where 1 in 30 games some of the enemies decide to wandering off the screen so you cant kill them. This may be a show stopper as I haven't been able to figure out why they are doing this. Or maybe Ill just have to hack in a backup plan so when it happens i direct them back. So yes currently its in a pretty mess but Im chipping away slowly.

As usual all graphics are placeholder.

I think I will post the next vid in the C3 forum as Ive been using C3 for a couple of months now. So bye bye C2 its been an awesome and enlightening trip.

https://drive.google.com/open?id=1PyBBskF44RJUFj0zeavRDsTdfi7FFb3N