One of the things I noticed with RCT3 which was different to previous versions was that when I click on a ride and look at what people think I have to wait much longer. Especially if no-one is using it.
I'd suggest opening the ride, going to the "what people think" tab, and just leaving the window open for a few 10's of minutes. Go into "fast time" if it makes it simpler.
I've certainly not had the issue that you are describing.
It might be worth re-checking the ride stats. I've had rides whose intensity, excitement, and nausea ratings have changed over time. Which meant people wouldn't ride them.
Can you upload the park you are having problems with anywhere? It might be easier to figure out what's going on by looking at the park itself. Failing that, let me know and I'll PM you my email address so you can email it to me.
hi thank for reply.
It doesn't seem to be any particular park this has happened to me 3 times since I started playing the game. I've played 3 parks since I got this. The park runs great for the first 3 years or so....the older the park gets the less people want to ride. Believe me when I say it has nothing to do with ride price or the ride's popularity. I've had extremely popular coasters just drop off and it always seems to happen around the same time. It happens no matter what....
It's happened to me on the Treasure Island scenario, Atlantis, and one of the safaris. It's aggravating since I'm then forced to use cheat codes for money simply because noone is riding for whatever reason.
Oddly enough it seems certain rides transport rides/sometimes a thrill ride will maintain a healthy amount of people going through it.
Let me reiterate something. I still have people riding the rides it's just oddly empty and hits my income. Popular rollercoaster Year 1 = 40-full, Year 2 = same, Year 3 = 10-40, Year 4 and on = 2-4 peeps
Basically after a certain amount of time it's almost impossible to make any money. I hover around 300$ and it just goes down then back up.
In any case it's aggravating. I thought for sure this was some kind of bug.