LC2-Rewrite feature request: Manual dialing.

[UniversalMigrator]

In the Stargate series, there were a few occasions where manual dialing was used to activate a wormhole between two gates. For this to happen, there had to be enough energy in the gate for the ring to "unlock" and allow dialing. One instance of this happens in the SG1 episode Prisoners. See also Torment of Tantalus and Nemesis.

The first part of this request would be being able to turn the inner ring of the gate via some non-DHD, non-CC or non-OC method. One thought I had for this could be redstone signals as these are readily available to anyone playing even on vanilla MC. For instance, a redstone signal into the right side of a gate could turn the inner ring one glyph clockwise, where a signal into the left side would turn the ring counter-clockwise. A redstone signal via either the front or back of the gate would "engage/lock" the glyph currently under the top chevron. Rinse and repeat for 7/9 glyphs.

The second part of this request would only be possible when a power system is back in place for LC2, to have the inner ring only be manually dialable if there is a certain level of power present in the gate itself.

This would only be possible to do on a Milky Way gate, as the Pegasus gate's "inner ring" doesn't actually move in the same manner.

[AfterLifeLochie]

As cool as a feature as this would be, I can see some serious implementation issues which would make it very difficult (if not impossible) to make it practical.

Firstly, there's no official association between the glyphs on the Stargate ring and that of the "official" alphabet; that is, the system doesn't consider the ring angle at all (and thus doesn't care about what texture is selected) - it just so happens that the textures line up properly.

Secondly, in lower resolutions it'd be impossible to see which glyph was selected currently at the top of the Stargates. Even more problematically, lower texture resolutions would make it almost impossible to actually read the glyph (event at high display resolutions). For this reason, it seems an accessibility nightmare to implement it so.

Personally, I would prefer to implement a "pocket DHD" if this suits you all better; it'll work pretty much the same way as the current DHD does and will require power (when that's a thing again), and will incorporate some (but not all) features in this suggestion.

[UniversalMigrator]

I pretty much figured it might not be possible, but thought I'd put it out there in any case.

The pocket DHD is a good idea though, and is even true to canon as well.

[Cronosus]

in sgc is used manual dialing too = computer, they dont have dhd.
if can be stargate powered instantly and dialed only with computer (dhd not required), then is this same as manual dialing.

[MrJake222]

I don't like idea with redstone, better would be clicking on blocks. I wrote about this on MC forum: It's stupid that the time of ring spinning is fixed, no matter actual symbol and target symbol. I suggest fixed ring speed. And to implement this, you need to know what symbol is on top. Maybe lock the resolution on highest(And what is highest right now?), or if resolution != max this feature will not be avaliable.

[Soyaro666]

lock resolution on highest (I doubt this is possible) could cause massive performance problems for slower machines. And I doubt anyone wants to rewrite the code to know which glyph is where. I guess that would require a full rewrite of the gates...

[AfterLifeLochie]

I wrote about this on MC forum: It's stupid that the time of ring spinning is fixed, no matter actual symbol and target symbol. I suggest fixed ring speed.

This is a different suggestion altogether, and is not really changeable.

Maybe lock the resolution on highest(And what is highest right now?), or if resolution != max this feature will not be avaliable.

This is equally as silly, because older systems could struggle to render (or even load) the texture on the gate; it's also equally as silly to make a feature unavailable because the host platform isn't fast enough.

And I doubt anyone wants to rewrite the code to know which glyph is where.

The system does know which glyph is where - it does spin and select them correctly currently.

I still don't see this as being a feasable feature, simply because it'd be so hard to use and would really defeat the purpose of having a DHD, computer or other dialling system.