- Joined
- May 18, 2020
- Messages
- 49
- Trophies
- 0
- Location
- Tkaronto
- Website
- virtual.dimensionless.space
- XP
- 456
- Country
Hey, GBATemp, it's been a minute.
I had a lot of free time yesterday with the Facebook/Instagram outage, and for the last few months of the pandemic I've been watching a lot of Star Trek Voyager and DS9, so I decided to use yesterday's sudden free time to pay a tribute to my favourite sci-fi soap opera by porting Star Trek Voyager: Elite Force Holomatch over to the Switch via the Tulip Voyager engine. It's about 95% or so complete in my opinion, just mostly requires some tweaks with the controls and bugfixes to get botmatches working properly (as currently they cause the game to softlock at the end of a match), and to get the game to stop crashing when it's placed in sleep mode. Crossplatform multiplayer works, basic gyro works and custom maps/mods also work. Keyboard + Mouse support also works if you want an authenticly 2000s twitch-based shooter experience.
Known Bugs:
Basic controls:
I had a lot of free time yesterday with the Facebook/Instagram outage, and for the last few months of the pandemic I've been watching a lot of Star Trek Voyager and DS9, so I decided to use yesterday's sudden free time to pay a tribute to my favourite sci-fi soap opera by porting Star Trek Voyager: Elite Force Holomatch over to the Switch via the Tulip Voyager engine. It's about 95% or so complete in my opinion, just mostly requires some tweaks with the controls and bugfixes to get botmatches working properly (as currently they cause the game to softlock at the end of a match), and to get the game to stop crashing when it's placed in sleep mode. Crossplatform multiplayer works, basic gyro works and custom maps/mods also work. Keyboard + Mouse support also works if you want an authenticly 2000s twitch-based shooter experience.
Known Bugs:
- Virtual keyboard shows up upon every launch. Not a big deal, but a slight nuisance to some people probably.
- Sleep mode causes the game and sometimes Horizon to crash. This seems to happen in a lot of ioquake3-based ports, and I'm working on diagnosing it.
- Solo Matches can't bypass the score screen, therefore softlocking the player. If this happens, press X to bring down the terminal, type "/quit", hit Return, then press Enter twice and it'll drop you back to HBMenu. Multiplayer & Multi Match bot matches works perfectly, though.
- Really epic battles can cause the framerate to dip on larger maps regardless of graphical settings. I'll try to work on optimizations, but I can't guarantee I can do a ton about it. Changing the resolution to one below 720p via the q3config.cfg file may help a touch.
- Gyro needs to be enabled/disabled from the console ("/in_gyromouse 1") due to a lack of menu options.
- You tell me.
Basic controls:
- Left Trigger - Alt Attack
- Right Trigger - Attack
- Left Bumper - Crouch (or brings up keyboard when text fields are selected)
- Right Bumper - Jump
- X - Use
- Y - Taunt / Toggle Console (menu)
- A - Select
- D-Pad Left + Right - Left/Right Weapon Select
- Dpad Up - Zoom
- Dpad Down - Toggle Console (in-game)
- Minus - Scores
- Plus - Menu
- Left Stick In - Vote No
- Right Stick In - Vote Yes
Last edited by faithvoid,