Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Ship Internals" section incorrectly describes grid coordinate axes #199

Open
rjwut opened this issue Apr 29, 2020 · 14 comments
Open

"Ship Internals" section incorrectly describes grid coordinate axes #199

rjwut opened this issue Apr 29, 2020 · 14 comments

Comments

@rjwut
Copy link
Member

rjwut commented Apr 29, 2020

Currently, it reads as follows:

A vessel's internal system grid is laid out in a 5 × 5 × 10 matrix: X (port to starboard), Y (dorsal to ventral), then Z (fore to aft).

This appears to be reversed for the Y and Z axes: it looks like Y increases ventral to dorsal, and Z increases aft to forward. I would appreciate it if others could confirm this.

EDIT: It seems like X is actually okay, but Y and Z still seem reversed.

@rjwut
Copy link
Member Author

rjwut commented Apr 29, 2020

If I'm correct, this should be an accurate diagram of the TSN Light Cruiser:

  0 1 2 3 4   0 1 2 3 4   0 1 2 3 4   0 1 2 3 4   0 1 2 3 4  x
0                 W           ·           W           W       
1                 ·       · A W A ·   I A · A I       ·       
2             · · A · ·   · · · · ·   · · · · ·               
3             I   ·   I   ·   ·   ·   I   ·   I               
4                 ·           ·           ·                   
5                 ·         · · ·       · · ·                 
6     ·         · · ·     M · · · M   M · · · M       ·       
7   · · ·       · · ·     · S S S ·   · · · · ·     · T ·     
8     ·         · · ·     · · S · ·     · · ·       · T ·     
9               · F ·     B F · F B   B · F · B               
z    y=0         y=1         y=2         y=3         y=4

@NoseyNick
Copy link
Collaborator

https://noseynick.net/artemis/snt.html is in the order actually read from the file
So PROBABLY:
X = port .. starboard except all the ships are symmetrical so I'm not sure we can prove that?
within each of those:
Y = deck 5 (top),4,3,2,1 (bottom)
and within each of those
Z = rear to front

@NoseyNick
Copy link
Collaborator

@rjwut
Copy link
Member Author

rjwut commented Apr 29, 2020

Technically, one ship is not symmetrical: the TSN Missile Cruiser has a stray hallway node just floating out there on one side. However, you can't really see a difference in the client. But I have confirmed by correlating DAMCON positions reported in the client against the protocol that X increases to starboard.

@rjwut
Copy link
Member Author

rjwut commented Apr 29, 2020

If we really wanted to, we could always create an asymmetrical ship... 😊

@NoseyNick
Copy link
Collaborator

Technically, one ship is not symmetrical: the TSN Missile Cruiser has a stray hallway node just floating out there on one side.

Oh you're right! Never spotted that before!
That's artemis-4.snt so https://noseynick.net/artemis/snt.html has the extra random corridoor. Is it fair to say front, port side, top deck?

@NoseyNick
Copy link
Collaborator

If we really wanted to, we could always create an asymmetrical ship... blush

I heard a rumour someone has made a Millennium Falcon 😁 🖖 😉

@NoseyNick
Copy link
Collaborator

Oh you're right! Never spotted that before!
That's artemis-4.snt so https://noseynick.net/artemis/snt.html has the extra random corridoor. Is it fair to say front, port side, top deck?

I can't see it on a real Eng screen... Perhaps because it's not actually connected to any other part of the ship, up/down/port/starboard/fore/aft? 🤷‍♂️

@rjwut
Copy link
Member Author

rjwut commented Apr 30, 2020

Dots are rendered at nodes where systems or damage exists, and corridors are rendered between two non-empty nodes. Since there's no system there and there isn't another non-empty node adjacent to it, there's nothing to render. What might get it to show up is damage: maybe try letting an enemy shoot at you with no shields to see if that node gets damaged and shows up?

@rjwut rjwut closed this as completed Apr 30, 2020
@rjwut
Copy link
Member Author

rjwut commented Apr 30, 2020

Oops, didn't mean to close it.

@rjwut rjwut reopened this Apr 30, 2020
@rjwut
Copy link
Member Author

rjwut commented Apr 30, 2020

Well look at that...

hallway damage

@rjwut
Copy link
Member Author

rjwut commented Apr 30, 2020

Oh, and confirmed that it's on the port side.

@NoseyNick
Copy link
Collaborator

front port but BOTTOM deck not TOP deck!
Updated https://noseynick.net/artemis/snt.txt and https://noseynick.net/artemis/snt.html

@NoseyNick
Copy link
Collaborator

NoseyNick commented May 1, 2020

So correct order is:
FarPort, NearPort, Centre, NearStarboard, FarStarboard (5 slices)
... within which...
Lowest, Low, Centre, High, Highest (5 decks)
... within which...
Stern .. Front (10)
... within which, the float x,y,z, int type, unknown (int?) u1,u2,u3,u4
Correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants