Jump to content

lot61

Members
  • Posts

    25
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

lot61's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Collaborator Rare
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

9

Reputation

  1. I found that a pickup action with type 0 (pickup) must be executed before a pickup action with type 2 (place) can be executed. Even if a staff member is hired with "autoPosition: false" so that they are ready to be dropped, the staff cannot be dropped by the API.
  2. I'm trying to use the following API to move a newly hired staff member, but I'm getting a message, "Can't place person here" in the game interface. executeAction(action: "peeppickup", args: PeepPickupArgs, callback?: (result: GameActionResult) => void): void; For the PeepPickupArgs, I can't find a correct set of values to make it work. I'm even trying to place the staff member where an existing staff member is. An example value using the coordinate of an existing staff member in Forest Frontiers: { type: 2, // 0: pickup, 1: cancel, 2: place id: 0, x: 1632, y: 832, z: 96, playerId: 0, } I've also tried dividing all coordinates by 32 just in case but that didn't work either. Can someone confirm if this API is working, and what is required to get the action to succeed?
  3. Originally there was a maximum of 2 guest spawn points. Recently in v0.2.1-1020 and v0.2.2-255, I noticed that I could place at least 8 guest spawn points. Then after I removed spawn points by shrinking the map, I was able to do this:
  4. A while back, @LordMarcel96 posted a video of the fastest coaster possible without cheats. I've now found a faster coaster. Since steep drops can gain more speed than vertical drops of the same height, I figured that there could be some speed gains to be made if that extra speed isn't negated by the slight extra time spent on the drop. This is also how I created a perpetual motion coaster. OpenRCT2 allows twister trains of up to 8 cars but RCT2 only allows up to 7 cars, so I assume that's why Marcel used 7-car trains. Using 7-car twister trains, I was able to achieve 389 km/h, a 5 km/h improvement over the previous. Since stand-up trains are faster than twister trains, I was able to achieve 400 km/h with 7-car stand-up trains. Then I tried floorless trains, which can go up to 8 cars in both OpenRCT2 and RCT2, and achieved 405 km/h. This is the fastest train among inverting twister trains subject to RCT2 restrictions and is in the attached park. If we use the vehicle limits of OpenRCT2 instead, the fastest inverting twister train is the 8-car stand-up. A lucky group of guests achieved 420 km/h. Even faster coaster.sv6
  5. If you just want to use other ride types in a park, you can enable debug tools in options under "advanced" to access object selection during play. If you open the scenarios in the scenario editor, the rides and guests will not be there. However, you can use the convert saved game to scenario tool to open a scenario. From there, change the object selection.
  6. All objects are available in advanced mode of object selection. Scenery groups have a real game mechanic in addition to providing organization; they can be placed in the invention list to be researched.
  7. Roller coaster graphs would be helpful during ride simulation. I would monitor them during "real" testing of incomplete tracks, especially to obtain perfect block timing by testing in continuous circuit mode. Sand bag testing would be great, too. I'm quite an unethical park manager in using guests as sand bags in crash-proof testing and would love to clear my conscience.
  8. It seems that the starting coaster, Flaming Fury, is causing the problem. Although its stats are already calculated, it seems that it can't finish recalculating them. I tried by updating the chain lift speed to clear stats.
  9. After saving, some 4 station rides will be blank in the ride previewer. When trying to build them, nothing happens except an empty ride construction window opening and, if money is involved, an immediate build and delete transaction. From my testing, it seems that a faulty saved ride can be made by creating a 4 station ride in a way such that station 1 of the saved ride would be longer than 2 segments, though I don't know if it's the only way. Original RCT2 seems to have the same problem but simply raises an access violation upon selecting the faulty saved ride. I've attached a save file with the same coaster in 4 rotations, with one station being 3 segments long and the others 2 segments long. The one named "4station fail" produces a faulty track file. I've also attached the faulty and non-faulty track files. 4station_testing.sv6 4station fail.td6 4station pass.td6
  10. Can you attach a saved game in which this behavior occurs? I think those stats usually require the beginning of a second run through the course to appear. If you set your ride to wait for a full load, then it may take a while for the second run to occur because few guests will line up before stats are out.
  11. In the original RCT2, guests will still queue for unsheltered rides in the rain if they are heading for them. In OpenRCT2, no guests will enter queues in the rain. Is this an intentional change?
  12. I think it shouldn't be difficult as long as the flat rides cover a wide enough intensity range. Some of the thrill rides are as intense as roller coasters.
  13. Maximum queue waiting time is a function of queue capacity and ride throughput. For tracked rides in general, if time is spent waiting for the next vehicle to arrive at the station for loading, then throughput can be increased by increasing ride capacity by increasing the number of vehicles or vehicle capacity or decreasing ride time. This will have no effect if vehicles are stacking up at the station while the ride is operating at max throughput. You can improve loading times by placing the ride entrance near the middle of the vehicle that is loading at the station so that guests don't have to walk far. I've made rides that were limited by how fast guests could get on the ride and get the trains going that supported 4000+ guests per hour and 100+ guest queues with less than 5 min waiting times. Also, long queues can cause themselves to get even longer because guests start checking their watches, causing them to stop in line and slow down the queue, sometimes to the extent that trains leave without a full load.
  14. Especially in queues because they are usually the only winding paths, handymen can turn back and forth when litter pops up nearby. Eventually they seem to snap out of it, but it often goes on long enough that the paths become absolutely disgusting. In a test that I did, the handyman heads back and forth along the marked path. This happens in vanilla, too.
  15. If you're in a particularly busy section of the park, the game may slow down if your computer can't handle everything. Then it will seem to speed up when you go to a relatively empty part of the park. On a related note, I noticed that when my frame rates drop to 30, roller coaster motion looks a lot more natural to me. At the normal 40 fps, everything looks a little too sped up. Then I noticed that in-game seconds are faster than real seconds by a factor of about 5/4, looking at coaster data. This is true in vanilla, too. Any reason why that is?
×
×
  • Create New...