RCT Discussion / OpenRCT: advantages and disadvantages

  • Liampie%s's Photo
    The launcher screen and the updates are getting blocked, because of something like this: https://www.reddit.c...r_it_also_pops/

    Sucks, I can't join Fisch's server now :(

    edit: Spent a while trying to fix it, but just after I posted this I figured it out. I set back my computer's clock a few days. Did the trick
  • janisozaur%s's Photo
    We don't do the launcher, we only provide builds.
  • Liampie%s's Photo
    Okay. So who's responsible for the launcher? And why doesn't it update? I don't really understand how all this works...
  • RWE%s's Photo

    Wow, the new rotation feature of the tile inspector is awesome! Good job!

  • spacek531%s's Photo

    You can skip the launcher by clicking on the OpenRCT2 executable in the bin folder where OpenRCT2 is installed.

  • Scoop%s's Photo


    Wow, the new rotation feature of the tile inspector is awesome! Good job!

    fuckin awesome!!! 
  • RWE%s's Photo

    Next a copy+paste feature and I'm in love. :D

  • janisozaur%s's Photo

    Okay. So who's responsible for the launcher? And why doesn't it update? I don't really understand how all this works...

     

    We have pretty much automated the process of producing new builds. We use AppVeyor & Travis CIs, which do a new build each time we push a commit. If said commit is on a specific branch (`^(develop|push/)`) then it gets pushed to openrct2.org as well. Both launchers use this domain as a hub for gathering information on which build is the most recent one and somehow (I assume) provide you with an updated build.

     

    We also have packages deployed to our PPA and to AUR, which, in my opinion, are far better, easier and more reliable software distribution systems than the launchers.

  • Steve%s's Photo
    I've just downloaded the most recent build and I'm experiencing an issue where the game just closes unexpectedly after a few minutes. I'm running on Mac OSX also but this never happened with previous versions. Am I missing something?
  • janisozaur%s's Photo

    I've just downloaded the most recent build
    That's not very specific. Can you say which one exactly? Can you post the park you're using? Can you bisect against any other good?

    Don't you get a (system-provided) crash report when it happens? If you do, please post stack trace.

  • disneylandian192%s's Photo

    To any of the Open RCT2 developers:

     

    What is the timeline to move beyond backwards compatibility? Is there the possibility of having two versions of Open? One that is backwards compatible and one that is not? Folks can choose to run one or the other with the understanding that, with one, it will no longer be an .sv6 file?

     

    I ask because, and I'm sure others want to know too, when we could expect things like a removed map data cap and other exciting features that we know are most likely not possible without moving beyonds backwards compatibility. I've got a project that I know will hit data limit soon, but if I know if I hold out for a few months or a year I can just keep working on it without any ability for it to be opened in vanilla. Will this even be possible to take a park on an .sv6 file and change it to whatever the new file type will be?

  • X7123M3-256%s's Photo

    Janisozaur said they intend to be free of vanilla code by the the next stable version (0.05), at which point the save format could be changed (I don't know at what point they actually plan to do this though). My understanding is that it's mostly drawing code that remains to be implemented.

     

    They have said in the past that when a new save format is introduced there will be a feature to convert SV6 files to the new filetype.

  • Liampie%s's Photo
    I hope it will be possible to keep playing with SV6's, only switching when an vanilla-incompatible feature is used.
  • spacek531%s's Photo

    Expanding on what liam said, it will probably be useful to have an option to lock out non-compatible features so that one isn't used accidentally.

  • disneylandian192%s's Photo

    Great idea! I know personally the features of Open have really sold me on the idea of moving beyond vanilla and would happily never go back if it meant having the things we've always wanted. 

  • Liampie%s's Photo

    Expanding on what liam said, it will probably be useful to have an option to lock out non-compatible features so that one isn't used accidentally.


    Please. I want to be able to combine OpenRCT with vanilla RCT. Both because I want people who don't own OpenRCT to be able to open my parks, and because I want to keep all the functions of the vanilla game and its trainers.
  • Scoop%s's Photo

    if they don't own it they can buy it for free.

  • spacek531%s's Photo

    Backwards-compatibility is something that I value a lot in other projects even though it isn't important to me Open/RCT2. I can totally see where liam is coming from.

  • BelgianGuy%s's Photo

    honestly, the moment they can get MOM in open rct there's no reason to keep using vanilla... that's the only thing they haven't added that I use vanilla for.

     

    if it could be added to the land tab that'd be swell since everything in MOM is decided through land colour that you get a dropdown menu in the selection of a land color or the tile inspector could actualy be configured to target a specific land colour to implement MOM with...

  • X7123M3-256%s's Photo

    8Cars used the land color in order to be able to locate the target tiles in the map data, as you can't add extra UI elements with a trainer. With OpenRCT2, there's no need to keep using land color in this fashion - instead, I think it would be better to have an area select tool of some kind - or maybe you could click on objects to select them (or possibly both?)

Tags

  • No Tags

Members Reading