Hi folks

hoping someone out there can shed a bit of light on the rather annoying problem I'm having here... has anyone else noticed that their code produces different results on different machines? Not simply performance differences, but actual visual differences in what is rendered?
Basically, I'm making a 100-metre-square room, where the walls are made from metal-cloth that you can leave dents in. The first 10 by 10 panel I made worked fine on it's own, but when I add the code for it to create ten, to cover one whole wall, the weird stuff starts.
On my desktop rig (2.71Ghz Dual-Core AMD, 2GB RAM, XP Pro Service Pack 3, NVIDIA GeForce 9500 GT w/ 1GB RAM, DirectX 9.0c), the second and third wall panels don't display, you can just see the backdrop through them. Dark Physics still recognises them tho, as you can walk into them. I was wracking my brains trying to work out what I'd messed up, then for the hell of it I put the whole lot on the laptop I just bought, mainly to see what the performance diff was. And guess what? Visually, it ran perfectly. All ten wall panels displayed, tho it ran very slowly. The laptop is a Fujitsu Siemens Esprimo Mobile with a 1.7Ghz Dual-Core Intel processor, 3 GB of memory, Vista Home Premium, an SIS Mirage 3 graphics board and DirectX 10.
Needless to say, this spun me right out. One one hand, it meant my code must be alright. On the other, it meant there was a problem I couldn't do anything about causing major havoc in my game!!!
I wondered today if it's a DirectX thing? But DX10 only works under Vista, so I'm out of luck if that's the case (tho I've checked around and no-where prior to me buying it did it say Dark Physics needed DX10...).
Anyway, I've attached the entire folder for this project, it's probably easier for people to have the lot and see how everything fits together rather than put lumps of code out of context on here

I'm assuming it's a Dark Physics issue as I've given stuff I've done in the past to people and they've not had issues with anything on their machines, this is my first project with DP so it's the prime suspect right now...
If anyone fancies poking at it and fixing my inevitable screw-ups, or knows the cause of this daft behaviour, please feel free to enlighten me!
Cheers,
Wolf
P.S> Yeah, the movement code is pretty crappy right now, sorry about that...