Not much. Think looks horrible. It's often missed, but how humans interact with a device is usually one if not the biggest factor to a successful product.

Technologists engineers and upstream users miss this in favour of technological evolutions. Usually with little consideration of how humans use a device.

This device takes what is making tablets and smart phones successful and mire the success in unsuccessful controls. ie controls that only sell to a small segment of humans with money.

senseg.com would have been a more worth while technology. This tech would keep the pure TS interface, yet then also provide the finger feed back missing. Then I admit stick some shoulder buttons on then it's good to go.

This machine is going to flop. that's my opinion anyways :)

Thanks. I had originally thought the dead zone value was in the plugin. When I noticed we could set it to zer0, then we/I could just create one in the event system.

But this is in fact way better to have a radial deadzone in the pluing itself. Thank you very much Ashley :)

Third

Websites are not a book. A book reflects light. A monitor generate light. I would like a DARK theme for both the website and C2.

I know the common belief that a white background is professional, but that entire concept is just mass subjective belief. Where as eye strain is has physical and behavioural effects.

Rory

Thanks, but I think that credit goes to Velotjet, his threads are popular and his instructions were translated to another language :D He has also been at it longer and more supportive :)

Tobye

If you want to PM or start another thread we can go over the matter. But my initial thought is that your going to have trust the clients.

Start a gruop timer. Then offer a "Ready" button. When everyone hit's the "ready" button. Then start the game with various timer passes for each computer. This is going to require some constant verification messages. ie, P1 is ready, p2 is ready...

Once all the clients are ready. Then start "Round count down" on each client. Once all clients have received a round count. Start the actual count.

Once the round count is done. Send the turns out done or not. Let the turn play out. Send a "turn done", once all has received a turn done. then repeat and rinse.

I have a question though. Is this a Squad game or each player controls 1 character?

I can go into more details else where :)

------------------

Also awarmenhoven and myself are talking about network gaming solution for C2. More specifically about the idea of C2 code running as logic server. Just keep an eye out in the "general game design" is where the idea will be presented and seeking input or interest.

LOL, NM. I never saw the property :D

I thought the deadzone area was defaulted with no access :D. With access that becomes another matter.

Ashley

There has been a growing thread on the Ouya developer forum regarding the software implementation of the Deadzone.

Ouya Deadzone problem

I remember using the gamepad for a PoC twinstick shooter in Construct 2 and noticed an angle problem. So like the last pages of the Ouya thread. I decided to write up a Construct 2 version of the test app.

The design of the app is that when the left analog stick is moving. A transparent dot will be drawn at the location. The result is that an apx a circle is drawn.

Ideally an image similar to this an XBox 360 controller

After testing the program. That is not the result.Construct 2 Test CAPX

The thread at the Ouya website linked to an article that suggests another way for doing a a different deadzone. Where the only the centre is dead not the along he entire XY axises.

Now I admit that I dropped the twinstick shooter I was doing for the Ouya in favour of only needing a pure left/right, but I thought I would still bring he attention that the current C2 deadzone implementation could use some work.

lemo

I will release the plugin shortly. Let me go over it to put in documentation for the source code. Remove anything that's unused in the ACE at this time.

DrGreenThumbCAN

hmm. I've been only using FF and Chrome for the majority of my playtesting. So this is a big problem.

First. The game uses North American WASD, with some EU use for QZ. There is no arrow key movement since default movement isn't good for networking. Aiming is mouse only. If there is a problem past this let me know what's in the console log.

Health is set to a max of 10. Picking up more won't increase health. So that's not a bug.

Tobye

Inherently you want some logic server to control timed turns. — Photon and my plugin do not have any authentication server going. However, i'm sure with some creative thinking we can find a solution :) Let me give it some more thought :)

How also adding reputation required. If you don't have 1000? 2000? reputation. You can't post a game. The point level should represent some level of activity with the community.

delgado

I suggest using scirra.com/forum/yetanother-multiplayer-demo_topic51622_page1.html . It seems the most ready to be functional for game developement. He has what it looks to be a server ready :)

for server details I suggest asking rexrainbow directly :) it's his server work :)

I need stop working on this game :D

* Added shooting sounds with distance based volume :)

* duplicate player seems fixed based on latest tests.

If anyone wants I'll post the photon plugin used for the game.

delgado

The answer is Yes. sure you can take this game online.

However, it's going to be a lot of work. I do mean a lot. If you need help please ask questions :)

However, i suggest doing some research.

* How much work are you willing to put in since you will be working mostly from scratch

* Are you going to Host the server on your computer

* Are you going to pay for a server

I'm willing to offer advice and help design the structure.

Assuming player has some kind platform or 8 directional movement.

Compare the stick XP(X Percentage) and YP(Y Percentage)

Compare Value stick.XP > 30

-- player.simulate(moveright)

-- player.setSpeed = absolute(stick.xp * 5)

Compare Value stick.XP < -30

-- player.simualte(moveleft)

-- player.setSpeed = absolute(stick.xp * 5)

... so on etc.