Messages

Not sure if it was from this same guy that we got the map I opened with Blender to extract the cars. Then from the CERV III, I generated a basic shape for Stunts and KyLiE worked on it to optimise it and then did the whole engine work

You've sparked my interest on this matter again with this. It'd be nice if for a whole year, we all tried our best with Default to try to update these scoreboards. I'd say we should do it in every style, mostly free-style and OWOOT, and with any car, but most importantly with the PMIN because it's the fastest of the original cars and the one that we have the most classic records with.

This is a good idea!  I originally made the shorcut keys to be comfortable, but never felt satisfied with the result. I have thought of Bliss 3.0 for quite a while, but I never have the time. Perhaps I could patch version 2.6 one more step, but there are some important things I also want to add and they do require a rewrite, so let's see what comes first

Packed pine tree groups look great there!  Stunts should have packed pine tree group elements

Saturdays normally would be easier for me, but I've gotten used to the fact that live races are usually on Sunday. I'm a bit more tired because I tend to sleep later on Saturdays, but I can make it

Ah!  Yes!  How come I didn't see it!

Very tough track! 

Oh!  I really would like to feature this one in R4K    Not sure how fun it is for a race. Is it available here or only via Google?

Great to watch! 

Well, my renderer shows wheels incorrectly for a different reason. It is true that the vertices in the wheel primitive where originally incorrectly guessed. My renderer does not calculate the rim widths this way. It's a fixed proportion.

The actual problem with rendering is that drawing ellipses is difficult and also slow. Of the different possible solutions, I chose to simplify wheels because my engine is already a lot of messy code. I would have to rewrite some things and also, it'd be slow. I have to find a more optimal way.

To be more specific, the current renderer uses a FreeBasic primitive ("Line") to draw almost everything, mainly triangles. Wheels can be drawn out of triangles by subdividing the drum into base polygons, but this would be very evident in high res. Stunts does it, but in 320x200, they don't need to be too many polygons and there's some simplification as well, yet not very noticed. If I use a very large number of primitives to prevent this, it gets really slow to draw them all.

There's also the "general ellipse" problem. An ellipse is a circle that you can stretch or collapse in one direction. If this direction is aligned with the X or Y axis of the screen, you can escape eliptic functions (which are numeric and very slow to calculate) by just using a factor on one of the axes. I could've used (and I tried to) this technique on the renderer. It would've given artifcats when there's a roll, but would've looked good otherwise. But I had issues that I couldn't solve without rewriting a reat part of the engine.

A general ellipse is one that's not calculated as a stretched circle, but as two foci and a distance sum, which is what an ellipse truly is. It can also be obtained by stretching a circle and then rotating, but that required again converting the ellipse to polygons. Not a trivial thing. Stressed does not draw its own ellipses (I am almost sure). It instead uses a some library for this purpose.

Ah!  I've got something I can share

Food

Indeed!  Just posting at the last time 

Congrats, @dreadnaut!

Well, @HerrNove shared a good amount of information I could use to sync it to Supersight. I haven't done much more on this now, but I would like to adapt the TSR to detect any Stunts binary if possible. If I find the time, I want to create a small server program to monitor a live race. Could be used to look at the map or to see it live in the 3D thing, but the latter is not fast enough currently to play that way, or maybe it is... We'll see