X7123M3-256

You can already make snowy parks, there's a snow land texture and some snowy trees. Here's an example from H2H8. I think this would be a nice feature and totally feasible, but it's unlikely I'll do it anytime soon because I have so much other stuff I'm trying to work on, and I tend to never finish projects.

@jessicajones SpaceK has more here if you haven't seen. He does a Christmas pack every year.

I don't plan to implement this right now - I have my own feature that I'm working on at the moment and it's likely to be a while before I'm done with that. This doesn't look like an especially difficult thing to do though, especially as the game apparently already has the snow sprite. Maybe when I'm done with the custom track I could have a look at it (and resubmit my old code for the powered ride cheat). I can see the issue you opened but it was closed as a duplicate. Sorry about that, I told you it wasn't a duplicate because the issue I found had been closed, but there was an even earlier open issue from 2015 that I'd missed.

That sounds less like missing data files and more like the program just doesn't work. Whether that has to do with your Android version or something else I do not know, I don't think I can really help you much more since I'm only going by what's written on that Github help page. If you don't get another response on here, I would suggest asking on the Gitter. The first thing I would try to do is try to get a stack trace. I'm not sure how to do that on Android, I guess it involves ADB.

It's the original RCT2 path which I think should be /storage/emulated/0/rct2. Yes, the path should be in quotes.

I don't have a lot of ideas because I've never used the Android version (few people do) and I'm not very familiar with Android either. At this point you are probably better asking on Gitter or waiting for another response on here. The only thing I can think of is that you copied the files across incorrectly. Did you copy the `data` folder itself into /storage/emulated/0/openrct2, or did you just copy the contents? I'm not sure which is the right thing to do, honestly, but try both. Yes, I would definitely fill in the correct path in config.ini

I don't know, I'm not familiar with Android development. It doesn't matter, they should be the same - I'm not sure why you would have two copies of the data files in the first place to be honest. Wait, are you trying to copy the executable?

Yes. You need to copy both the OpenRCT2 files and the RCT2 files to their respective directories.

Just write a brief description of the feature, suggestion, bug, or whatever. You may want to include the link to the old issue for context. If you report a bug make sure you specify the version of the game you are using and the steps needed to reproduce it, otherwise the bug report is of little use. From what I can tell, the guy who made it submitted a PR, but there were issues, and he ended up deleting it instead of fixing them. It's sometimes the case that a PR is submitted, but there are problems (e.g it doesn't merge cleanly with develop, doesn't compile on all platforms, etc), and can't be merged straight away. I had a feature I implemented to let you change the speed of powered rides, which was never merged because I messed up the rebase and never got around to creating a new PR. As far as I can tell, the guy who submitted it later deleted the code (not sure why), and it was not suitable for merging in its current state anyway. If it was just a matter of merging it, that would have been done back then, there was still more work required. Also, this was in 2016, and the codebase has changed a lot since then (back then it was mostly C, it's now C++), so a refactor would likely be required. Also, I am no more capable of asking the developers things as you are.

I don't have an executable for Windows because I don't use Windows - I only have a Linux executable. If you want a Windows binary, your best bet is to ask @Spacek because I know he has compiled this program for Windows. SpaceK has also written a guide on how to compile the program and general use of the tool here. The compilation process is much easier on Linux, Windows is a pain in the ass. I had originally planned for the program to be easier to use, but as I said, it was never finished and became too buggy to continue working on. The rewrite has been long overdue, but has barely started and probably won't be done for a while. I am also working on custom RMC track and an updated RMC train model which is taking up most of my time at the moment. The new version will probably be more basic, but less buggy and with much higher quality output. As I did with the original tool, I'll probably add functionality as I need it. This is the alternative tool to which I referred - https://github.com/oli414/Blender-RCT-Graphics. It only renders the graphics (it won't create a DAT), but it does a much better job of it, and with OpenRCT2's support for JSON objects, you don't actually need to create a DAT file to get them in the game. As a side note, if you are unable to get a suitable tool running, you can send me your 3D models and I can make them into a custom object on my end.

No, you shouldn't lose any savegames unless you explicitly delete them. The launcher will overwrite the openrct2.exe executable and the OpenRCT2 data files, but not the user data like scenarios, track designs or custom objects. If you are changing the OpenRCT2 data files (this means g2.dat and/or the JSON objects), you'll want to either keep them separate from the launcher or not use the launcher at all, but you shouldn't need to change them unless you're adding new features to the game.

I don't think so, they should all be playable - just missing certain rides and land textures that were present in the originals.

That page you linked is all the information I have as I have not used the Android port. It says to place the RCT2 assets (if you have OpenRCT2 working already, you can look in config.ini to see where these are located - otherwise, it's the folder that contains rct2.exe) in storage/emulated/0/rct2, and the OpenRCT2 data files (i.e g2.dat and the JSON objects) in /storage/emulated/0/openrct2. The Android version should also support RCT1 as it is exactly the same as the desktop version, but that page doesn't say where the RCT1 assets should be placed. I guess you could try /storage/emulated/0/rct1, but if that doesn't work you can try asking on the Gitter (or wait and see if someone else gets back to you on here).

Looks like it was already suggested, and actually implemented, but was never merged. See https://github.com/OpenRCT2/OpenRCT2/pull/3636. Since there doesn't seem to be an open issue for this you could still submit another if you wanted - that was back in 2016..

Feature requests are better posted on the Github issue page. You can post them here but not all the developers will check this forum regularly. You can also have a go at implementing this yourself and then submit a pull request - it doesn't sound too hard. Someone did make something similar, but that's just changing the ground texture.

It will automatically download and install the latest build of OpenRCT2 if there has been an update since you last played the game, and then launch the game. It's just a helper tool to keep the game up to date (since updates are frequent) - the version of OpenRCT2 that you get is the same one you would get downloading directly from the website. It also lets you switch between develop and release builds easily. As for installation, I think you just unzip the folder and run the executable, but I haven't actually used it in a long time, there might be some additional step.

Go to the red toolbox, select on "Open custom content folder", and it should direct you to the correct place. On Windows this will be Documents/OpenRCT2/object, and on Linux it's ~/.config/OpenRCT2/object. I wrote that program. Why can't you compile it? Do you get any errors? Are there files missing? Or do you have a binary that just crashes? That program was never quite finished, and is a buggy mess, so I wouldn't be surprised if it just segfaults on you, honestly, but I know that it has been successfully used by SpaceK (and me, of course). Also, the renderer is pretty poor quality - you're probably better off using Oli414's Blender addon instead. The link you posted is the only download link I have for that program (I post all my stuff on Github). It should contain all the source code, and if stuff is missing I can try to fix it but honestly it's been years since I've looked at it and I'm currently in the process of writing a new version.

I'm pretty sure the lighting effects only work with the rendering mode set to "Software (hardware display)" and not with the OpenGL renderer. That was definitely the case when they were first added, and I have just tested on a very recent develop build, and cannot enable the lighting effects in OpenGL mode. If I enable them and then switch to OpenGL, they do not function. However, I was told by one of the developers recently that they did work with OpenGL - though that might have been in error. You could always submit an issue querying it. Also, the light effects were severely broken until a couple of months ago - so if you are using a release build you will want to switch to develop if you plan to use them.

Yes. But they'll be opened in RCT2, so they won't be identical to the originals (some RCT1 rides weren't in RCT2, for example). I believe that improved RCT1 support is planned, but some features will require the new save format (which is currently being worked on). Expansions for RCT2 are supported (since they're just a collection of content with no actual changes to the game, there's no way they wouldn't be). I'm not sure what the expansions for RCT1 were - as I understand it OpenRCT2 should be able to open all RCT1 parks.

Wait, I found an updated Android build - this is from four hours ago as far as I can tell. Looks like the Android builds must have been fixed since the last release version. EDIT: Actually, you don't even have to look there, you can get it from the download page on this site. I didn't look there before. This is the latest develop version.

Disassemblers are the tools used for this kind of reverse engineering. The OpenRCT2 wiki mentions both IDA and OllyDbg, so I assume these were the main tools used. I wasn't involved with the reverse engineering so I don't know the details. (I did start disassembling some code but stopped when I realized it wasn't the one I wanted. IIRC the code I was actually after was among the last to be decompiled). Anyone could do it. So far, nobody has done. There exists an OpenGraphics repository, but it only contains four rides and hasn't been updated in three years. There's over a hundred thousand sprites in g1.dat alone, so this would be a big project.

It is possible to install OpenRCT2 on Android, but few people do because it's hard to play on a touchscreen. The Android port isn't very well maintained because so few people use it, and the last release version I can find with an Android build available is almost two years old, so you might have to compile from source (unless there's a more recent binary out there somewhere). This page has more information, including the correct location for the RCT2 asset files, which will have to be copied onto your device.

I'm pretty sure the files on disk are in an archive format and need to be extracted before they can be used with OpenRCT2; I don't think pointing OpenRCT2 directly at the disk will work. If you are able to run the installer, this is likely the easiest way to get the files you need (all it really does is extract the files and copy them to disk), but if you can't run the installer because you're not on Windows, you should be able to use other archive software to extract the files. Just check what format they're in (I think it might be *.CAB) and look for archive software that can open it. If the files are not in an archive, then you can use them directly. You want to select the directory which contains the rct2.exe executable (which you don't actually need), and the subdirectories"Data" and "ObjData".

OpenRCT2 was written by reverse engineering the original game executable and reimplementing it in C (and later C++). The original RCT2 source code was never available to the OpenRCT2 developers; they worked only from the binary. For the first two years of its existence, the OpenRCT2 code would call into the RCT2 binary for any functions that had not yet been rewritten, allowing the game to be reimplemented piece by piece while retaining full functionality. By the end of 2016, all the original code had been replaced. OpenRCT2 is now completely independent of the RCT2 code, but still uses the assets from the vanilla game.

They're not missing, they aren't supported. I think the only RCT1 sprites that OpenRCT2 currently supports are the wall types, but this may change in future. You could make the paths into a custom object and use them in RCT2 that way - someone may have already done this, but I don't know. RCT1 paths work a bit differently to RCT2 paths though, so it wouldn't be exactly the same.