Jump to content
OpenRCT2
  1. OpenRCT2

    1. 2,611
      posts
    2. 6,640
      posts
    3. Parks

      Show off your parks or join community park projects.

      7,009
      posts
    4. 1,051
      posts
  2. Multiplayer

    1. Multiplayer Discussion

      Complaining about griefers? You're not the first.

      381
      posts
    2. 164
      posts
  3. Community

    1. News and Announcements

      Announcements regarding OpenRCT2 and our community.

      179
      posts
    2. Introductions

      Perfect place to say 'Hi'.

      656
      posts
    3. Small Talk and Offtopic

      For anything that doesn't fit the other forums.

      1,387
      posts
  • Who's Online   1 Member, 0 Anonymous, 22 Guests (See full list)

  • Forum Statistics

    2,394
    Total Topics
    20,157
    Total Posts
  • Member Statistics

    3,594
    Total Members
    372
    Most Online
    REDNECK2020
    Newest Member
    REDNECK2020
    Joined
  • Posts

    • It's written in C++.
    • @Gymnasiast What code does openrct2 use?    
    • @jensj12 The gyazo link is just a screenshot. @Smp017 OpenRCT2 defaults to scenario unlocking, where the first five are unlocked and you can unlock more by finishing scenarios. If you just want all of them to be available at once, you can do that by going to Options -> Miscellaneous tab (6th, with a slide icon) and unchecking 'Enable progressive unlocking'.
    • You're welcome! By the way, this should now have been fixed. If you like, you can now put the game back on software rendering mode (OpenGL mostly works fine, it sometimes has minor bugs and it cannot yet draw previews of track designs, but that's about it).
    • I'm not the boss of these forums, nor a moderator.   You fork the project on Github, do your changes, then a button will be visible in the Github web interface. But of course, you'll have to know how to code to do so.     Anyway, there was once talk about a central authentication server. When word of that came out, someone came to our chat channel and started a not very pleasant conversation about how we shouldn't (let's say he started becoming angrier and angrier and used unparliamentary language). After that, nothing happened, as we had a load of other stuff to do. I cannot promise anything, but we _might_ revisit this once we finished doing work to reduce the number of desyncs. A lot of work has gone into it already, which has hopefully made a noticeable difference already, but more is to come.
  • Popular Contributors

×
×
  • Create New...