So, I've been tracking down a "bug" in MV3D where the PC's movement on the client is at a completely different speed than on the server. I've seen the bug for quite some time now, and it makes moving around in game relatively hard and annoying. I just ran a test that printed something every time the physics was calculated. It should have happened ( Read more... )

Things that I'm unhappy about leaving out from the first open source MV3D release:

• Trees and Grass. They got lost in a refactor (since they were a hack) and were never reimplemented correctly.
  
• The in game editor. It's dead Jim, kick it if you don't believe me. Implementation sucks anyway.
  
• More stable data storage. Not that I've had any problems ( Read more... )

So, one of my upcoming tickets that I've been forced to think about is moving around the package layout of MV3D so that it makes more sense. The current layout is not very pythonic, there's a lot of modules named the same as the classes they contain, lots of implementation in __init__ files, etc. Here's my first whack at reorganizing it:

( Read more... )

I just finished up the new authentication code for MV3D. I'm very happy with it. It works similarly to my last post, more or less. A client establishes two way trust with a login server, the login server creates two random passwords and a unique identifier. The client logs in to the desired server using its username, unique id, and the first ( Read more... )

So, mitre_box pointed out some holes in my authentication scheme. Apparently authenticating two untrusted entities via a third trusted entity is tough. Also, PB doesn't support what I was trying to do anyway. Here's try #2 ( Read more... )

I keep making these tickets to do what I think will be fairly straight forward things, and then once I start getting into them, I realize that it'd be better to do a whole lot of refactoring and cleanup. The little ticket suddenly becomes a multi-week or multi-month project. I'm stuck on one of those now, actually ( Read more... )

A little while back, I noticed that the way logging in was handled on MV3D servers was rather terrible in the security department. It wasn't completely horrible given the network design it was built for. Originally, MV3D was going to be only run on servers I controlled, so trusting the servers with a lot of things was more or less ok. However, now ( Read more... )

.. that's what my wife keeps calling me for obsessing about the Wiimote. One of the big things I wanted to do with the wiimote is be able to estimate its position/rotation when it can't see the IR LEDs. It isn't possible to do this very accurately, but I was able to put together a program that does this. You can even use it with the nunchuk. It can ( Read more... )

My bluetooth adapter came in today, so I've got lots to say now that I've actually used the wiimote. My original plan to go from wiimote to Python was to use GlovePIE to redirect the controls to PPJoy (a joystick emulator), and then just read the virtual joystick using Ogre's input system or pygame ( Read more... )

Phew! I think I finally have persistence worked out in MV3D. I'm quite happy with it. I went back to my datastore method (yes, I saw that cringe), but I feel like I've made it quite a bit better. One of the reasons I couldn't say no to it is that it's lightning fast. All the other methods I've tried (all of which involved a database of some sort) ( Read more... )