Pode's Forum Posts

  • Ashley : is it going to be easy to add support for various things via the plugin system ? With node, it's easy to add functionnalities. Are we going to have explicit support for disk access, or embedding other "node-*" things in it ?

  • Ga2Z : i'm going to update the behavior soon. I'll check those bugs at the same time.

  • That kind of effect can be achieved with a Posterize shader.

  • Kyatric : I need to find a discussion I saw about it. Chrome dev are planning to integrate something like that into the engine. (I'm pretty sure I didn't hallucinate it <img src="smileys/smiley2.gif" border="0" align="middle" />)

  • You do not have permission to view this post

  • It's not simply WebRTC that's needed. There's also the need of a solution added on top of that to discover available devices on the same network (�la Bonjour/mDNS), or do something to punch holes inside firewalls, to work without a central server.

  • sogen : that kind of solution isn't needed anymore on iOS, since there's WebAudio API available.

  • rexrainbow : the HTML5 video tag allows it, but it depends on the browser, the OS and the codec. Since most video codec are designed to stream a few block of images, display them, and do that chunk after chunk. That means that depending of the combination of sources listed above, the display can be choppy, or even not working at all.

  • rexrainbow : that means that the rounding of the position is done on Firefox and Chrome, but not IE. I'll check what's special with it.

  • rexrainbow : I'll check it when I'm back home.

  • rexrainbow : thanks for the info ! <img src="smileys/smiley2.gif" border="0" align="middle" />

  • newt : I didn't try. Logically, all the character are safe, even if they can't be displayed by the browser. However, you need to use a character that isn't in the Asian plane of Unicode/UTF8/UCS2/and all that... I think you are on the safe side if you choose a punctuation characte (like ';' or '-'). I can't test it right now, so tell me !

  • Arima : it's not the best solution, but you can apply a simple encryption algorithm when saving string, like ROT13, for example. With that, the player won't access any sensitive information when reading the source.

  • There's also a problem with Pointer Lock API that isn't addressed for the moment : the pointer acceleration. Since the workgroup decided that they don't take it into account, I can imagine a lot of games were it's going to do some strange behaviors, since the mouse pointer is going to have a non-linear acceleration.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • rexrainbow : you're right, you need to load it into in image and paste it.