3 ms·
It looks really cool (I love the flat poly aesthetic), however some hopefully helpful feedback: - Framerate isn't wonderful (20 - 30 fps on my laptop, which wi
by bartread 5y ago
It looks really cool (I love the flat poly aesthetic), however some hopefully helpful feedback:
- Framerate isn't wonderful (20 - 30 fps on my laptop, which will happily run graphically more intensive JS demos at 60fps usually), and I see you're using React: is using a relatively heavy framework the best way to go here? Possibly this is fine and the optimisation is required in other areas instead (e.g., are you creating loads of garbage?),
- Car physics and handling is way off: clearly for this game realistic handling probably isn't the goal, but it's bad by the standards of more recent arcade racers (Burnout et al, Cel Damage for something that has a slightly similar aesthetic), or 1980s style 2D racers like OutRun (or more recently 80s/early 90s-esque racing games).
It's certainly an interesting demo - and, as I say, I love the way it looks - but in terms of demonstrating ClojureScript as a viable platform for game development, definitely needs more work. And in terms of this being a game, it's a long way from that: no objectives, no other drivers (depending on the objectives, may or may not be required), no hazards, pickups, etc., no sound, and so on.
- ertucetin 5y agoThank you for the great feedback! The goal was just to show the ClojureScript version of the original demo (the first version of it). So there is no collision detection, sound, etc. I think ClojureScript has too many things to provide in this field.
- bartread 5y agoIt's definitely an interesting demo and certainly not the first time a less obvious (i.e., imperative) language has been used in game dev: just today on a separate discussion people were talking about use of GOAL (a compiled dialect of LISP) in PS1 game development. Pretty cool stuff.
- rkangel 5y ago> I see you're using React: is using a relatively heavy framework the best way to go here? If you read the README, React is kind of the whole point of this demo: "This project is a showcase for the feasibility of React in gaming." We'd need to know the cause of the performance issues to know whether it has succeeded or not!
- bartread 5y agoOh, sure, but I did point that out. I'm suspicious of React but open enough to realise the cause could be any number of other things.
- brundolf 5y ago> Framerate isn't wonderful (20 - 30 fps on my laptop, which will happily run graphically more intensive JS demos at 60fps usually) Something I'm curious about is whether the frames are dominated by game logic (ClojureScript/React) or by graphics. If your laptop doesn't have a discrete card, and the author hasn't taken steps to optimize the graphical side via culling, etc, then your fps may not be representative of ClojureScript/React-based games in general
- bartread 5y agoDell XPS with both onboard and discrete graphics. Funnily enough I just tried it on my 2015 MBP, which likewise has two GPUs, and - ridiculously - it runs much more smoothly.