Openrct2 custom content

broken image

There's no need to guess, it, I have the projection matrix and the angles you need to set the camera to if you want them.ĪE says several things are hardcoded that are not actually hardcoded at all. It's a well known projection that was/is common in 'isometric' games (it is not however a true isometric projection). I wrote my own renderer to handle all this for me but that's probably overkill depending on how many sprites you need to render (some of my rides have tens of thousands).ĭon't just guess the camera angle by trial and error. Also, the colors that AE marks as remappable aren't actually the remappable ones. I don't - it will get very tedious if you are doing a ride as they have lots of sprites. Otherwise, you might end up with non-remappable colors in remappable areas. When you are converting to indexed color, if your object is supposed to be remappable don't include the other color indices in the target palette. I wrote my own renderer to handle the process, but that's probably overkill. Render first to true color, and then convert. You're palletizing the image twice - the resulting quality loss is evident in several of AEs rides. Don't render to a GIF and then convert to RCT2's palette.

broken image