Initial thoughts and issues

[xHyperSteve]

In my haste to get this program going I accidentally nuked my own setup. Not a big deal because I have other setups now.

So I quickly setup NES and I was very surprised at how quickly the games ran, and just started working after point to the folders. It was a far cry from the old days. I liked that very much! Honestly great work  team!

 

 

Couple of issues I'm having on this Windows 10 system:

- The new HyperHQ seems to but opening multiple instances in the task manager. And does not close properly unless I go in and "End Task" them.

- The startup time on Hyperspin loading roms and assests is slow. No biggie for NES but I'm curious how long multiple systems will take.

- Curious about shaders and how they could be implemented within HyperHQ

 

No deal breakers at all, I'm grateful!

[fr0stbyt3]

- HyperHQ uses multiple processes within a single instance. This is common for multi threaded multi process applications. Chrome, Slack, and discord look and work the same way for example. When you close the app, it minimizes to the tray. This is also fairly normal for modern applications. In our case, it leaves a process running to accept downloads from HyperTheme. In the future is will act as a plugin host as well. To close the app, right click on the icon in your task bar and select quit.

- The rom matching process is CPU/Disk bound. So slow hard drives and older CPUs may have slower performance. But I believe the issue you are having is download speed for new media. A release coming out in a few days has an update for download speed.

- Shaders in HyperSpin/HyperTheme are coming very soon. We're going to implement them in the same way other features have already been added to the theme builder with a full UI for configurable settings.