Gymnasiast

The entertainers costume dropdown has bugs. I noticed that a few weeks ago, when working on code for random entertainers.

I see some of you plastering their desktops with icons Anyway, here's mine:

I think you probably installed a 64-bit version of OpenRCT2. This version is not yet finished and only intended for testing and development purposes. You should install the 32-bit version of OpenRCT2, that should solve the problem.

@jensj12 You need to turn 'sort by track type' on in order for it to work. (Or use a type of train that enables steep slopes itself.)

Accusing us of things we haven't done, seeing everything as a personal attack, refusing to cooperate, being egocentric and playing the victim are all very troll-like behaviour. I wonder if wolfreak has ever asked himself why he has been banned so often and if that wasn't down to his behaviour.

There are so many things wrong with your post, it's hard to say where to begin. First, the allegations towards us. Contrary to what you said: we haven't threatened banning you. In fact, we have been very permissive, choosing to ignore many bad aspects of your behaviour rather than banning you for it. Also: we haven't brushed you or anyone off: we simply want to implement things properly, and we have made it very clear from the start that multiplayer is not anywhere near release quality. You keep accusing us of all kinds of things, we have ignored it so far but our patience is running out. Most projects would probably have banned you a long time ago. Despite all our patience, you keep putting up a bad attitude. Then, about your code quality: it's not as good as you, or the people that say you're one of the best devs, think. Far from it. Anyone calling you one of the best devs clearly hasn't seen your code or doesn't know much about programming. We have offered you numerous times to look into it together, but you even refuse putting features into separate branches and opening PRs for them. And then you have the guts to complain we don't accept your features in the game. How are we supposed to do so if you flat out refuse to cooperate? In short, you have a bad attitude, you refuse to cooperate and you vastly overestimate your own contributions, but somehow it's all our fault. You're playing the victim here. This will get you nowhere, not on the internet and not in real life. Cut it out.

Always report bugs and crashes to Github. Except when they're already present of course, but there is a search function for that. When in doubt: report it anyway.

There is also a difference between how the number shows up and how it is interpreted. Expect some strange things to happen since it's an undefined state, but it shouldn't crash. BTW, there a cheat to renew your rides. That will get rid of strange built dates.

Update to a more recent operating system. (XP support is not a priority and not tested, although some people have compiled versions that do run.)

An explanation: an assertion is basically explicitly stating an assumption, which will trigger errors like these if they happen not to be true (rather than failing silently or in a less obvious), to make for easier troubleshooting. Thanks for reporting this. You can track its status on the page Broxzier pointed to.

Could you upload that file, so we can test why it crashes?

I would run with --verbose on first before opening the can of worms that is compiling.

You cannot expect help if you don't provide vital information, like your OS version, or where you downloaded your zip files (openrct.net or openrct2.com). Or whether you have RCT2 installed.

Probably because you cannot write to the Tracks folder of your RCT2 installation.

That's not what I meant though. Can you provide a save/landscape that I can load and will definitely trigger a crash when I go back to Object Selection?

Have you been able to save that landscape before you clicked to go back? Or, if you haven't, do you have steps that will trigger the problem? It doesn't happen in every case, as I just tested in in my own install.

The idea of not including WW or TT objects is that not everyone has bought these expansion packs (not surprising, as their quality is way below RCT1/AA/LL/RCT2). Though it wouldn't hurt if some scenarios did use WW or TT objects, in my opinion. As for Erik's scenario: it looks nice. And having a park feature around which the player has to build a park is a concept that RCT1+2 readily used. It would need some interesting terrain and a town of some sort, IMO. And having some sort of theme to the park (water-based?) would be nice. Having good scenarios in the store and/or in-game is very important in my view. At some point I would want to create an official OpenRCT2 scenario set, with the best user-created scenarios, and an official extended scenery set, with things like roof corner pieces.

And how exactly? Rune can't get rid of limitations imposed by SV6, you know. Neither can I or any developer until OpenRCT2 switches to its own save format.

Welcome! Ah, the Zygorators from Canary Mines. I have fond memories of them.

Ugh, why can't I edit my posts after a few minutes? That forces me to double post. Please change that as well. Anyway, what I wanted to suggest is making the forum resemble (Open)RCT2 more in terms of appearance. In a similar way to what OpenRCT.net and tt-forums.net do.

Some points still: Why is this topic listed under Small talk and not under Feedback? I'd say that is the proper category. Is the forums software capable of handling multiple languages? If so, would it be possible to give users the option of using the forums software in Dutch? There is quite a big chunk of the user group from The Netherlands and posting everything in English is already hard enough for some people.

Removing the rank and keeping the dots would have my preference then, though I'm still not convinced it says that much. I have seen so many obnoxious long-time users on forums over the years.

I don't really like the obsession with the number of posts anyway. As if people who talk a lot automatically make more sense. I'd say get rid of them, as well as the posts count next to every post.

This error seems to be gone now.

Clicking a timestamp in the recent posts column will give one an error message.