On a work trip, I would like to get back to a game after the day is done. I already have a portable display I enjoy using. The less dependable part of my experience has been the internet connection available at the hotel.
In my August and September notes, I described the frustration of trying to use Remote Play while traveling. By October, I wanted to turn that recurring complaint into something more useful: a record of the connection I actually encountered and what it was like to play on it.
What I want to record
I plan to save speed-test screenshots during future stays and pair them with a short account of the gaming session. The useful record would include:
- The hotel, city, date and approximate time of the test.
- The connection I used, including whether it was the included Wi-Fi or another option.
- The device and test service, with the original screenshot and its reported measurements.
- The game or service I tried and whether I could connect, keep playing and use the controls comfortably.
- Any sign-in trouble, interruptions or change in the experience during the session.
I want the numbers and the account of playing to stay together. A screenshot will show what the test reported at that time; the accompanying notes will explain what I was trying to do and how it went.
What a stay can tell me
My notes should describe the stay I experienced. If I return to a property, I can compare the new visit with the earlier one instead of treating one evening as a permanent rating.
I also want to keep the equipment story separate. My glasses can remain useful on a flight, train or as another screen even when a hotel gaming session is frustrating. The portable-screen account covers that experience.
The next step
This is the plan for the next round of travel notes. I have not yet added measured hotel results or ratings to this collection. Those entries will need the actual screenshots and my account of the stay.
Based on my August–September travel-gaming notes and the October 28, 2026 plan to document hotel connections.
Record the point where a session stops
A future stay can be described as a short sequence: join the network, complete any sign-in, reach the game, begin playing and see whether the session remains usable. Recording the point where the sequence stops would make an unsuccessful attempt more informative than simply calling the Wi-Fi bad.
The notes should also distinguish an interruption from an uncomfortable but continuous session. Being disconnected, waiting for a game to start and finding the controls difficult to use are different experiences. If I repeat a test, the record should say what changed rather than quietly replacing the first result. This would give readers something concrete to compare across stays, while keeping the account tied to the room, time, equipment and game actually tried. The test remains planned work until those observations exist.