Two Odd Issues

[Eddie]

I have been running 0.0.4 on two different PCs running Windows 10.  They have identical Options set.  OpenRCT2 works fine on one of the PCs.  On the other one, the Save Ride and Save Ride with Scenery don't open a file naming dialog. 

On the same PC, some pre-invented rides do not show up in some scenarios.  For example, in Botany Breakers, jet skis, trams, river rafts, rowing boats, swans, and tri-cycles do not show up on the PC with the save problem.  Then, one PC has a Hypercoaster and the other has a Corkscrew Roller Coaster with the same button icon - and one PC has Rowing Boats and the other Boat Hire.  All the DAT files are there, and I'm not sure what to check next.

[Broxzier]

That's strange, it should run exactly the same if everything is the same. Can you try running the game with --verbose, maybe that prints some helpful information to the console.

[CharlieP]

Check on the opening page Options Menu under the gears and make sure the "Select rides by track type (like RCT 1)" box is checked. This will cause the coasters to show up differently.

[Eddie]

There are two differences showing up in the logs in start up.  First, the PC with the problems uses forward slashes in the file addresses, and it seems to be missing a second and third set of object loads after the begin openrct2 loop.  I've bolded the lines before and after the difference.

PC1:

VERBOSE: Source_Sample::LoadCSS1(C:\Program Files (x86)\Atari\RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 59)
VERBOSE: Source_Sample::LoadCSS1(C:\Program Files (x86)\Atari\RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 60)
VERBOSE: Source_Sample::LoadCSS1(C:\Program Files (x86)\Atari\RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 61)
VERBOSE: Source_Sample::LoadCSS1(C:\Program Files (x86)\Atari\RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 62)
VERBOSE: begin openrct2 loop
VERBOSE: HardwareDisplay: false
VERBOSE: Source_Sample::LoadWAV(C:\Program Files (x86)\Atari\RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css2.dat)
VERBOSE: loading scenario details, C:\Program Files (x86)\Atari\RollerCoaster Tycoon 2 Triple Thrill Pack\Scenarios\Afri
ca - African Diamond Mine.SC6

PC2:

VERBOSE: Source_Sample::LoadCSS1(C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 59)
VERBOSE: Source_Sample::LoadCSS1(C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 60)
VERBOSE: Source_Sample::LoadCSS1(C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 61)
VERBOSE: Source_Sample::LoadCSS1(C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css1.dat, 62)
VERBOSE: begin openrct2 loop
VERBOSE: HardwareDisplay: false
VERBOSE: Source_Sample::LoadWAV(C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\Data\css2.dat)
VERBOSE: loading required objects
VERBOSE: loading object, C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\ObjData\MFT.DAT
VERBOSE: loading object, C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\ObjData\BALLN.DAT
VERBOSE: loading object, C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\ObjData\BURGB.DAT
VERBOSE: loading object, C  ( ...continues for about 800 lines, then...)

VERBOSE: finished loading required objects
VERBOSE: loading scenario details, C:/Program Files (x86)/Atari/RollerCoaster Tycoon 2 Triple Thrill Pack\Scenarios\Afri
ca - African Diamond Mine.SC6

 

NOTE:  Changing the game_path on PC1 from using forward slash to double back slash (as it is on PC2) didn't fix the issue.

Edited July 1, 2016 by Eddie
Also...

[Broxzier]

Another difference is that for PC1 all paths use backslashes, and for PC2 they use normal slashes. Try changing the RCT2 path directory to use backslashes on PC2.

[Eddie]

I did try that and there was no change in the outcomes.

[Duncans_pumpkin]

Are you sure they are both running the same versions?

[cascadia]

8 hours ago, Duncans_pumpkin said:

Are you sure they are both running the same versions?

Just to make sure, Duncan is referring to the build number, NOT the version 0.0.4.