Re: maxseer initial release demo
I do want to report that most of the text was read through system tts, but every now and again, a string or two would be read by NVDA instead. Maybe I was pressing something to switch them, but I'm not sure.
This is because of a known bug in NVDA that causes it to not say text if you're pressing down on certain keys. Since most NVDA applications are based on key presses instead of key holds (like moving around a room), this usually doesn't cause any issues. As a workaround, it switches to SAPI. I will reach out to the NVDA developers when the max-engine gains more momentum.
I was able to find my way around for the most part, but I had a hard time understanding the pathfinder
The pathfinder is a bit broken. Basically, it makes a grid where there are collisions and forms a path if it can find one. However, sometimes it makes the grid incorrectly and can't find paths properly. When it does make a path properly, you can hear it move away from you in a certain direction. When you follow the path, it makes a constant steady tone, but when you move against the path it makes a more jagged tone.
I tested the pathfinder last night and found some areas (especially in the Foyer) have issues with the pathfinder so I'll be investigating that on the next release.
What would it take to begin looking into placing this on top of an existing game?
In this example, when data is read from the XML file, it creates two kinds of data:
- Maxseer info data
- Map data (if necessary).
Lets look at collisions as an example since they're used by both. The object that stores the collision data before being loaded onto the map is here:
https://gitlab.com/labadore64/maxseer/b … ionData.cs
Collisions in maxseer only need polygons to define their boundaries so it loads the same polygon data as the collision does, and it creates the collision and adds the maxseer collision at the time of being loaded. Likewise, when the map is unloaded, maxseer's map data is cleared.
While this demo is very simple, you could add these components to any object. For example, lets say you have objects defined in an xml file, you could add a property that allows you to add a label onto that object, so every time that object is spawned, a maxseer label is also spawned. There is a lot of parameters that allow the end user to customize behaviour, such as whether or not labels are added to the navigation menu, ect.
Also, devs can define their own maxseer classes for custom interfaces if they need to, by inheriting the maxseer interfaces. In fact the SoundController is an interface so that it can be redesigned with a custom engine.
So basically, devs take their currently existing collision data shapes and transform it into an array of polygons, and feed those polygons into the maxseer engine, to load the collisions.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
