Gymnasiast

Zaxcav's pull request has just been merged. The new build should be available soon.

I'm quite certain this limit was there for performance reasons. Obviously, the performance concerns of 2002 are quite different from the performance concerns of 2017. So I think we could raise it to 12 or something.

The FPS count does not have anything to do with how fast things run, although more FPS can easily give that illusion, especially if you had low FPS before. Apart from that, I think Jens is probably right.

Flat rides are cheap and easy to replace. If it's 2 years old and broken, it makes sense to just demolish and replace them, since you will also be able to ask more money for them. In such a case you could get away with setting their intervals at 1 hr. On the flip side, breakdowns are never good for guest happiness.

Most people on the OpenRCT2 chat are from Europe. This could very well be the same for multiplayer. Judging from the time he logged in, the OP might be from the US. When it's 21:00 on the East Coast, it's already 02:00 in the UK and 03:00 in Western Europe. You're not going to find many people active from those parts then.

Oh, this is preposterous! How did you get the fucking nerve to call us lazy? We put months of our spare time into a game that we provide for you to use for free, and we haven't been paid a single penny. You haven't contributed a single bloody thing and yet you still think you can talk to us like that? Did you know you can fix stuff yourself and open a pull request? That's what open source is about: helping to create a better game, not whining that someone else should fix it. We have hundreds of people helping us out, whether that's in code, documentation, bug reports or even just general discussion. You have done nothing. And here is a thing: you don't have to. We don't mind if people can't contribute. The only thing we expect is to be treated like people. For you, even that appears to be impossible.

The diagonal flat-to-steep slopes have now been added to the Junior Roller Coaster. They were actually in RCT2's files (but the regular flat-to-steep slopes weren't!), but needed code in order to use them. RCT Classic doesn't support steep slopes on the Junior Roller Coaster. Most instances in the RCT1 scenario have been replaced by the Mini or Spiral RC in RCTC. (Which is technically more correct anyway.)

Thanks for uploading your saves, I'll investigate them. Error like this usually pop up when the game tries to draw a sprite ("image") that is invalid. It does not have anything to do with terrain types as imlegos suggested, as those are not saved as sprites anyway. Also, the error "unsupported RCT 1 sprite type" is not fatal, as that is only printed when the game detects an error like this and fixes it. It's one of the other errors you got.

Which build of OpenRCT2 are you running? The build hash is 7 characters long and it's displayed in the title screen. It looks something like 12a45b7.

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.