Screenshot / SS Track
-
23-February 18
- Views 6,885
- Fans 6
- Comments 40
nedesigns
- Copyright © 2002-2024 New Element Designs
-
Community Forum Software by IP.Board
He's working on a toy box pack. Should be fun!
YES. You and Spacek (spelling?) are making childhood dreams come true. This is so cool.
I know it's pointless, but I actually think it turned out really well. I might revisit it when I have inversions.
YYEEEESSSSSSSSSS. This is bringing back so many memories. I need to go finish my coaster. It's still half completed.
Thanks for putting in the time and effort on new objects and rides!
I managed to find the RMC track .png files, but they don't show up in-game. What do I need to do to make this possible? Also, I can't wait for the Toy box pack. It looks great.
If you aren't seeing anything at all, check that you are you are on the branch rmc_track and not develop (this is displayed in the bottom corner of the main nenu screen). If you are not, run "git checkout rmc_track" to switch to the correct branch. If that branch doesn't exist, you probably cloned the official repo instead of mine. After switching branch, you will need to rebuild the game and the g2.dat file.
If you see "Hybrid Coaster" listed in the track type menu, but the track is still invisible, you probably have the wrong track type selected. I accidentally added a duplicate name, but only one has the actual code. Test with the RMC save file I uploaded previously and see if that works.
If you are seeing RMC track but you want SS track, check that you have the correct sprites.json and that you have run "make g2" to generate a new g2.dat (you then have to copy the new file into the "data" directory for it to take effect).
Yeah, but when I opened your Forest RMC park file, the track was not there at all. Plus, the coaster crashes after a couple minutes. So, what should I do? Should I at least wait for an official release of the track splines?
This would generally mean you're using the wrong build (the RMC track goes in an otherwise unused track slot, so if your game doesn't have the track it will be invisible).
When you start the game, what does the white text say in the bottom left corner? It should say v0.0.8-rmc_track. If it says v0.0.8-develop, you likely have the right fork but the wrong branch. If it says v0.1.2-develop, you have the official build and need to download the fork I linked.
If you are definitely on the correct branch but the track is still invisible, I'm not sure what's happened. The only think I can think of is that you might not have the right g2.dat, but this would usually cause an instant assertion failure upon trying to load the park.
You could try sending me the binary you have compiled and I can see if it works on my end (as long as you're not on Mac because I don't have one to test on).
That's odd. Not sure what would cause that.
Here is a screenshot of the coaster with the missing track.
Beautiful!
I don't need to see a screenshot because I know what it looks like when it doesn't work. In order to help you I need to know what branch you're on, because that's the most likely reason for it not working.
If you won't answer these questions, the best I can do is list off possible reasons why it might not work. Can you at least check in src/openrct2/ride/coaster and verify that it contains hybrid_coaster.c?
I have checked that I can clone that repo and get it working, so I know it's not missing anything. All I can think of is that you're on the wrong branch, or you switched to the right branch and forgot to recompile, or perhaps you tried to recompile but the build failed for some reason (if this happened it would print an error). The easiest way to be sure which version you're actually playing is to look at the build number on the menu screen.
Must be a coincidence!
I'm using version 0.1.2. I think there should be a reasonable step by step process,with images, in order for someone to be able to have either the RMC track or the SS track. I'm sorry about how I'm behaving right now. It's just that I work better if I'm given proper instructions beforehand. If that I need to wait for an official release of the track, fine by me. I can't believe it will soon be available and very excited to eventually use the SS track.
If "using version 0.1.2" did not involve compiling the source code of OpenRCT2 in some way (visual studios, gcc, clang, etc.) then you are on the completely wrong track to getting the SS track.
He asked what you did so that he might tell you what to do, and that question has not been answered. Here are some other questions to narrow down what you did:
- Did you download the git repository on your computer?
- Did you use gitkracken, github, git bash, or other git client to switch the repository to the rmc_track branch?
- Did you compile the source code into an application?
- Did you put the necessary sprites in the necessary spot?
- Did you run the compiled application?
OK, this explains why the track isn't working. Version 0.1.2 means you are using the latest official version of OpenRCT2 and not my fork. I forked from version 0.0.8.
You first need to clone this repository (note that it says X123M3-256/OpenRCT2 instead of OpenRCT2/OpenRCT2). Then you need to run "git checkout rmc_track". This switches to the branch with the custom track. Run "git branch" to check which branch you are currently on. Finally, you need to compile the game and g2.dat.
The complete sequence of commands to download, compile and run the RMC fork (on Linux) is:
git clone https://github.com/X123M3-256/OpenRCT2
cd OpenRCT2
git checkout rmc_track
mkdir build
pushd build
cmake ..
make
make g2
cp openrct2 ..
cp g2.dat ../data
popd
./openrct2
You should then be able to open the RMC park and see the track.
I mean, if you really want images I can provide them, but it'd just be screenshots of me typing the above commands into a terminal. The problem you're having is that you're not using the right version - once you've downloaded and compiled the fork I linked, it should just work.
When the RMC track is done I'll submit it a PR for it, and it's up to the development team to decide if it should go in the official release. I won't submit a PR for the SS track - it doesn't make sense to use up slots on something with so few actual use cases.
You know what, since this seems too confusing for me, I'll just wait for an official release. I'm a very patient guy, so that when it is released, I would be ready to put it to good use.
Quark Offline
Why does everything you post fucking legendary?