Rough Lag When Placing a New Track

[SleetFire]

Since update 0.0.6 when placing a new track design on the map (you know, the white ghost or flashing version) the games lags really bad.

Anyone else experiencing this?

[jensj12]

I haven't noticed any lag the last time I built something. Can you try different graphics settings (render engine, build marker), and if it makes any difference, post which one lags for you?

[SleetFire]

I tried different render engines. No difference.

I'm not sure what build marker is.

 

However I did notice it only occurs on placing really big tracks. For ex. 'Titan' or 'The Goliath' from Sixflags cause lag. My large custom rides caused lag too. But small to medium tracks are placed smoothly. This makes me wonder if maybe it's just a personal computer issue.

Hopefully this is narrowing down the problem somewhat...

[SleetFire]

If anyone else is having this same issue post away.

As for now, it seems like a small bug so I'm not going to drag on about it. The game is still playable regardless.

[Broxzier]

@SleetFire Are you still experiencing this bug with recent builds?

[SleetFire]

Hello

I just tested it on 0.0.7 build 6b3b494. Placing tracks are smooth and steady, no issues to report.

But currently the 0.0.6 stable version is still a problem.

I've got a question now:

Are we better off playing on the most recent builds or sticking with the stable versions?

 

[cascadia]

1 hour ago, SleetFire said:

Hello

I just tested it on 0.0.7 build 6b3b494. Placing tracks are smooth and steady, no issues to report.

But currently the 0.0.6 stable version is still a problem.

I've got a question now:

Are we better off playing on the most recent builds or sticking with the stable versions?

 

Always use the most recent builds- they have many more bug fixes and features. 

[SleetFire]

Okay, Great! Making the switch.

Originally I thought the development versions would crash a lot and have issues with game saves.

[jensj12]

If the game ever has a major bug, it will be in the develop branch. However issues in the stable branch may have already been fixed in the develop branch. If releases start rolling out more frequently staying in the stable branch may be worth it.

Note that, once custom save formats are implemented, there may be issues with saving in the develop branch, but should have already been tested before even making it to the develop branch.

[Broxzier]

4 hours ago, jensj12 said:

If releases start rolling out more frequently staying in the stable branch may be worth it.

Which is exactly what we're aiming to do since 0.0.6 If you don't want to risk corrupting your saves (worst case), I suggest to keep using the stable builds.

[SleetFire]

Appreciate the detailed answers.

I'm concerned about reliable game saves (even got these things backed up on google drive) so I'll stay on stable for now. I think these files are like the heart of RCT in general. We must keep them heathy.

[imlegos]

Never seen a file corrupt before.

Though, should we switch to a new file format, the files will be openable in ORCT2, but after saving they can only be used in ORCT2

[cascadia]

5 hours ago, SleetFire said:

Appreciate the detailed answers.

I'm concerned about reliable game saves (even got these things backed up on google drive) so I'll stay on stable for now. I think these files are like the heart of RCT in general. We must keep them heathy.

 

I wouldn't really worry about corrupt files.  I've never seen it happen ever before. 

[Duncans_pumpkin]

Develop does still have the occasional game corrupting bug that slips in every now and then. I would trust stable more if you are worried about corruption.

[janisozaur]

s/stable/release/