willneedit / altspacemres Goto Github PK

Something like "&hide" to add into the Dial Computer's MRE URL to make it conceal its own address.

When an incoming WH comes up, the chevrons light up off by one.

The self location code needs rework.

1. Each component finds out the space it belongs to on its own
2. If an ID is given in the MRE URL, take that one
   a. Else look up in the database to see if there's an ID registered to the given location
   b. Failing that, create an ID out of the location
3. Look up the database if there's a registration for the new ID
   a. If there is and it is locked, fail the stargate initialization.
4. When the ID had changed, register the location with the new ID.

Since the dialing sequence is asnyced, it must be something else. I think I saw the animation go wonky when the player left, perhaps it's a rejected promise or something like this.

As a workaround, I could track the userID of the user who starts the dialing and do a force reset whenever said user leaves.

Could be a good idea anyway to mitigate trolling.

The letters on the DHD could still be a little bit closer to the center, better matching the hitboxes.

Check for stale timeouts of prior wormhole engagements or the sequence counting.

A player leaving has the chance to crash the Stargate while dialing. Provide for a clean cutoff.

Store dynamically added worlds into the provisioned Postgres SQL database, omit the bootstrapped world for space preservation.

Reason: The Node.js webhost seems to reset dynamically generated pages when being idled and restarted, disallowing the saving of dynamically added worlds.

Address handshake sometimes took too long/needs a reenter.

(Save info by Session ID?)

Transition over to a kit based modeling, away from Gltf.

• Full Unity feature set (Sounds, particles, bump mapping, shaders, ...)
• Transfers load from MRE to Altspace CDN

Move the core functionality of the stargate operational code (dialing sequence governance, event horizon establishment and disengaging) into a base class, keep only the bits connected to the design and layout (how the dialing sequence is displayed) within the current class.

Turn around the letters in the upper half to have them readable from the front view

When an incoming wormhole is canceled, the chevrons on the receiving end didn't go dark again

There's still the unresolved issue of obtaining the Gate's worldspace ID (either textual or teleporter style).

Getting the root transformation would be a bonus, but not strictly needed.

Filed under microsoft/mixed-reality-extension-sdk#104 , there seems to be an issue with the client where users who have already left still try to maintain a connection to the MRE. If the space falls empty and they become the 'authoritative' users over the space, they lock up operations.

Perhaps I need to build a banlist that would deny users and their IPs the service on a low level.

Error 503 (Bad Gateway) doesn't seem to deter these clients, else switching the MRE into maintenance mode would have done the trick. Maybe a different error code?

Swap deletion and creation of Event Horizon objects.

When someone starts typing, provide a timeout that only he can type for a given amount of time (30 seconds) without others interfering.

As long as we cannot read out the actual scaling of the Stargate we need to pass on a size parameter to make the event horizon fit to scale.

Idle connections time out at roughly 55 seconds, too quick for the sixty-seconds heartbeat.

When more than one user is in the room, the DHD isn't correctly initialized and registes double keystrokes.

(Sync buildup of the collider panels?)

Remove the need to have an enclosure. Ideally, it would be just plopping down the Stargate and Dial Computer of your choice to get things up and running.

• Enclosures will cease to work as soon as the old three.js/a-frame implementation is gone.
• Lowers the bar for world creators. No editing the world definitions needed anymore
• Obsoletes lots of inter-app communication

The portal needs to be redone using Actor.CreateFromLibrary("Teleporter:...")

Analysis needed:

• How to obtain the target space ID? It's a different one than the one seen in the Setting menu? Any relations? Deteministic GUID, perhaps?
• Migration: Transition between old and new IDs. Converting? Database table?

The Stargate MREApp would have to send messages to the portal A-Frame app to play sound effects at crucial moments.

1. Start spinup (whirring)
2. Spin (whirring/grinding noise)
3. Chevron locking in place (cha-clack)
4. Voiceover (Numbers 1 to 9, engaging and error message, perhaps different soundsets)

Create an event horizon model with "idle" animations as well as animations for opening up the unstable vortex (morph target, if possible) and the event horizon closing.

Check if these animations can be started/stopped using an MRE.