jensj12

You can scroll with the right mouse button and turn off edge scrolling if accidental edge scrolling is an issue. It takes some time to get used to but has worked great for me. If you want to keep edge scrolling, increasing the scale factor might help to improve mouse accuracy.

It's a RCT1 scenario, which means that, at the time of creation, flat rides couldn't be built underground, only tracked rides (for which the check works properly).

OpenRCT2 requires RCT2 to run. You have a disk of RCT1 (which is still a nice bonus for OpenRCT2, but not enough to run the game).

Remember to use giant screenshots when showing an entire park. I can easily recognize 3 of the prebuilt rides, but it's hard to see your own work.

Changing the appearance of guests is not as easy as you think. There are many, many, many sprites that have to be replicated for every variation, most notably the coaster sprites which show two guests in a single sprite and has to be replicated for every possible combination of variations. As this is done in the coaster sprites, all vehicle objects (including custom ones) have to be updated too, creating a ton of extra work for all coaster vehicle creators. Adding guest variations has been ruled out by the devs. It's not going to happen.

I think the image list got corrupted. It should be fine again if you reload the park (and maybe close the game in between). If it consistently happens in some circumstances, please explain how you can reliably get into a corrupted state. (for reference: #6073)

I think this has to do with CPU architecture. A possible cause would be trying to run a 64-bit (x64) program on a 32-bit (x86) machine. Can you try a different version from https://openrct2.org/downloads/develop/latest to see which one works? (try ARM64 first, then x86. Ignore the miscellaneous build at the bottom, you don't need that) This is sadly not a setting you can change in that launcher.

Side-friction coasters don't derail in corners or downhills. They only derail when transitioning to a more downwards facing slope (top of hills). Iirc the limit is 30mph, which is ~45 km/h, but I could be wrong about that, and it might even differ for the different track pieces.

An option like that would definitely be considered a cheat. I'm not sure if disabling guest weather preferences is already a cheat, but you can already force the weather to be something that doesn't decrease ridership.

If you run the game as headless server, it doesn't even need RCT2 linked. You only need RCT2 for the sprites and sounds.

That's because the track design contains elements that are not et supported by the track design save format, in particular the large corkscrew pieces (those were added by OpenRCT2 and not available in vanilla RCT2). Either save the park, or remove the large corkscrew pieces from the ride to save it.

In the options, enable the cheats top toolbar button. Then, in-game, a golden shovel should appear near the top-left. Click+hold it and select 'disable clearance checks'.

The game should never reset the entrance fee all by itself. If the entrance fee is set to free by scenario rules, you shouldn't be able to change it in the first place. The only thing that can modify the entrance fee for you are plugins, so please temporarily disable all plugins you have and see if the issue persists. OpenRCT2 is built upon the RCT2 engine, but has a cheat to enable the RCT1-style of charging both entrance and rides fees. This cheat is automatically enabled upon opening a RCT1 scenario and will likely someday be added as regular scenario option. (btw, what is ECT?)

Development progress can be found in the corresponging GitHub issue: #19152 In case of a rollercoaster: there is/was a bug that created ghost stations when the station was modified while simulating (blue flag). See #5244

Looking good. I can clearly see the inspiration from the original scenarios in some but they look for sure a lot more challenging than what the original game offered. Be wary though the sometimes extensive use of the mountain tool is clearly visible in the terrain (though even the original scenarios had that). Now I only wish the game had custom scenario tabs and packs like these are a perfect fit.

Please don't open 3 topics about the same topic, one is enough.

The original tabs are there if you have rct1 linked. If you're still missing anything, please elaborate.

The automatic windows build failed and therefore didn't get uploaded. It is just a single build that failed, but no new pull requests were merged in the last two days. It is possible to download the artifacts of any successful build, but I don't know how. The release build also still works.

The top piece of a chainlift is considered the end of a block section. So splitting the chainlift into two chainlifts with a small flat part in between is the way to go. If that hurts the looks too much for your liking, consider increasing the chainlift speed instead (even beyond the usual maximum with cheats if necessary).

With #19553 closed, this should be fixed now.

There is indeed a regression on the develop branch. For now, you can continue without this bug on the release branch and track its progress here: https://github.com/OpenRCT2/OpenRCT2/issues/19553

OpenRCT2 should be able to load any park using RCT2 objects even if you somehow don't have them. By clicking the download button, the game will attempt to download them from the nedesigns site. If you recognize anything from the list as RCT2 objects, you probably have a mixed install (files from different OpenRCT2 versions, remove and install OpenRCT2 to fix that). If they are custom objects, I can't help.

If a mechanic is just moving back and forth, it usually means that it can't find a path to the exit of the ride. In most cases, it's the path directly at the exit of the ride that is not properly connected. Rebuilding that piece of path should solve the problem in that case. If that doesn't help, please provide some more information like save/screenshots.

One thing to try is a fresh install, removing the plugins is just one part of it. As long as there's any way to make the game run, we can try intermediate steps to see where it crashes. So if you're willing to try, rename your entire OpenRCT2 documents folder with all your saves, plugins, custom objects, title sequences, settings etc. If it runs, put it back and find the offending subfolder by renaming some of them. I hope that helps.

The crash reports section of GH isn't flooding much more than usual, so I still suspect there's an issue on your side. Can you pinpoint any of the crashes listed HERE as yours? (maybe after sending another one) Seeing there are some recent crashes related to plugins, have you tried running it without any plugins installed?