Open ddorstijn opened 11 years ago
And don't mind seeing no ground again. :-(
And by the way a little question: Are you the one who made three.js?
Woah, I haven't seen that before. What do you mean exactly by "dive over an obstacle"?
And no, three.js was made by the very talented @mrdoob.
Image to explane. sorry for my drawing skills.
Okay, thanks for drawing it! I'm afraid I have no idea why it's happening, and it doesn't happen for me, so I can't really do anything about it for now, sorry. :(
Just spent about an hour trying to reproduce this, and couldn't make it happen. Change anything to potentially fix this since this issue was created?
I haven't made any attempts to fix this particular issue, no. Were you able to reproduce it earlier, @RestingCoder?
(edit: though various things have changed, so it's possible it's been "accidentally" fixed.)
Unfortunately, I just found this, so no. I'll see if I can make it happen under different browsers/OS. I'll let you know, and if I am able to reproduce it, I'll see if I can fix it as well.
Great, thank you!
Just a question. Are you still working on this game? And if you are: How is it going with the objects in gaming and what kid of changes have you done meanwhile?
Not related to the issue, but I was wondering if there is anything abnormal I need to do in order to get this running on a local server to work with it? Probably not, but I wanted to be sure.
Edit: Nevermind. Got it running with no major issues.
Another question though is: Can you provide some documentation regarding getting a model into the game? I'd be more than happy to make new ones, but I have spent the last few hours trying. First, I was getting errors, but now they are just invisible. I still collide with them though.
Tinkered with the three.js converter output, but it just didn't help.
Thanks!
Running on a local server may actually be difficult at the moment because of MongoDB dependencies. You'd have to set up your own instance.
I'm working on a cleaner HTTP API (eg https://triggerrally.com/v1/cars/ArbusuG) which is already in use by the editor mode, but not yet by the drive mode. The drive mode update should be ready within a week or two.
Once that's done, it should be possible to build and run the client locally and point it to this API.
For new scenery models, you need to use the three.js blender exporter in "scene" mode I think. Do you see any console errors?
Alright, so a 'scene' mode export looks a lot better, thanks for that. I am not a fan of Blender. Fortunately, I can use Maya for modeling, and then export it with Blender.
(I would just export it from Maya, but the format of the three.js export is WAY different when done from Maya.)
I've met a little bug when testing the new release.
In first person cam the screen flicks sometimes when you dive over an obstackle. I can imagine you see the window of the car at that moment because the camera got a little knockback.
Here is an image. It was really hard to capture the little flick but it worked after ten tries.