chewey

This is just a post of heartfelt gratitude towards everyone involved: The Alpine Coaster is a pretty awesome addition – thank you! I'm particularly impressed by the individual braking behaviour. It's quite fun to just watch, especially with the occasional traffic jam created by a particularly slow guest. You rock! 🥳

Oh… Oh! OooOoH! - Thank you! I've never considered this use of the cut-away tool, because… well… water is obviously deep, isn't it, so you would just see deeper parts of it. But yeah, it totally makes sense for the water rendering to just be a surface. This still leaves "lots of water on different levels" a case better solved by a global water hiding switch. I'll bring that up as a feature request. Thanks again, you've kind of revolutionised my underwater building already!

First off, thank you so much for OpenRCT2! This is pretty much the greatest thing happening to my gaming life ever, and keeps memories from close to 20 years alive. There's one feature request (not as in "demand", but as in "oh boy would I be happy if that were added") I'd like to voice: A switch to completely hide water, as is already possible with land via "Hide Base Land". It can become really tricky to build stuff underground if it is under water as well. I have resorted to "click counting" in the past, because visibility in this case is very poor. Since transparent water already exists, I'm hoping for this to be not too difficult to implement: Just make the transparency 100%… Is this something that would be seen as a valid feature request on github?

Ok, thank you. Will do 🙂

My apologies – I now realise that my post reads much harsher than I intended it to be. It was meant to convey my exasperation (I've encountered exactly this "never mind" thing way too often recently). I didn't intend to be or appear uncivil at all. Sorry.

For f*s sake! PLEASE mention what your solution is, even if you consider it an easy or obvious one! There's nothing worse than finding forum entries for a problem one encounters where the only reply is a version of "never mind, I fixed it".

I've just noticed how expensive it is to run a mini golf course, [attachment], especially when compared to a much bigger and more complex rollercoaster. This makes it unexpectedly hard to run such a course making a profit. I consider this obviously disproportional, and even a bug, and assume this to be from the original game. Would changing this be within the possibilities of OpenRCT2? I haven't found any running cost related entries in rct2.golf1.json…

Ah, thank you. I had looked for an existing github issue, but apparently my search terms sucked. No idea how I manged to miss "pricing", sorry.

Inspired by this tool from next door: How about a cheat option that makes ride prices automatically adjust to the maximum price peeps are willing to pay?

There are - occasionally but regularly - graphical bugs where rides clip through scenery (or the other way around). I assume most of them to be original bugs, but can't verify that due to lack of Windows. I'd be happy to report those as bugs on github. How would the devs like this reporting to be done so that it makes the most sense for them? One report per scenery/ride pairing, or a "group bug", or something else entirely? At least one class of those bugs might very well have a common cause somewhere: When clipping only occurs while a ride vehicle moves somewhere close by.