Great job!! mayhamurasaki

I have also been working with the native multiplayer plug in quite a lot. To fix the private/public room, I just made the 'instance name' private or public.

- Game name: Fun_Game_v2

- Instance name: Private

- Room name: BobsGame

Do you have any issues with the Scirra server? Ie; Does it run consistently or does it slow down?

Do you use mostly sync options, message options, or an equal balance of both?

How do you deal with players that have very poor internet?

Hi friends,

I have been having an issue where a late-coming peer (joining the game after the others have started) is unable to receive 'client update' trigger and/or set its client input state.

- Everything works just fine if all the host/peers join at the same time

- The late-comer peer is able to see the syncd movements of the other players

- If I disable the 'on client update' trigger, the peer can locally set the setbits, but is still unable to 'send' this data to the peer via the 'set client input state'

Any ideas what could be interfering with the 'client update' trigger but at the same time not interfering with the object sync?

I have one more to add to my wishlist:

- synced strings variables in multiplayer

Ok let's dream :p

- A web 3D engine

- Live co-editing (à là Google Docs)

Yesh, thish.

In my opinion, ARVR is going to replace all things with screens and 2D will be relegated to ever smaller use cases. C3 just has no way to compete in this potential future. This is a real shame, because I absolutely love the Eventsheet system and just the whole vibe I get from Construct. The Scirra team has done a great job of translating all the unnecessary code shtuff.

But again, if Scirra wants to stick their head in the ground and continue their line that 'Construct is a 2d games engine' then they will be increasingly less useful as time goes on.

With that said, I do think they are trying to figure this out. I recently started playing with the 3D objects and I think they are pretty cool. And, I say all this in love <3

Could you please provide this c3p again? I am super stumped on the same issue.

Did you make any progress with this?

For me, the same code works the same way in both iOS and Android:

You don't need javascript, here's a way to do it with events. It uses the tiledbackground object to draw it, and uses some math to do the raycast calculation.

https://www.dropbox.com/s/s8mz4i34djr89xy/raycast.c3p?dl=1

Kudos to construct for giving access to collision points. I didn't use the line of sight raycast feature since that doesn't provide the necessary data to do the texturing.

Also since events are so slow I tried utilizing javascript instead:

https://www.dropbox.com/s/b6hy5e5f3xdldmz/raycast_js.c3p?dl=1

It's much faster, even though it does the same thing. But man was that unpleasant to get working. Once i got past the syntax errors, i had to deal with all the silent errors that made it not work. Anyways, it's a shame js is needed to make things faster.

Duuuude! You're amazing! Thank you for those. It really helps me to wrap my head around the concept. I booted up both and the only difference I could really see is that in the JS version the boxes looked far smoother. Where as the C3 one seems choppy.