dummkopfofhachtenduden / silkroaddoc Goto Github PK

Hello!

Please help clarify where exactly object's collision is stored in BMS format.
At first I thought SR has just bounding box based collision but I see some collision mentions in NavMeshObj too. Or it's a different thing that needed for NPC navigation?

Is there some simple way to identify whether object has a collision or not? (checking some flag or offset)

1. Any information about how SR parameters (such as normals, position, uv) relate to other software?

2. Is there any other factors besides normal value in BMS format that affect how normals will work in game?
   I made custom bms file for tests (attached it here - chinaman_adventurer_face.bms.txt ),

I've used the guidelines described below but it still looks broken in game. I've tried to inverse axes during normal calculation but got the same results.

In-game:

Blender:

What I've learned experimentingis that SR has left-handed coordinate system with Y up.
So the formulas to convert parameters to Blender (right-handed coordinate system with Z up) are:

1. Blender Position = SR Postion.xzy * Vector(-1, 1, -1)
2. Blender Normal = SR Normal.xzy * Vector(-1, 1, -1)
3. Blender UV = (SR UV.x, 1 - SR UV.y)

Maybe we should put it somewhere on the wiki?

Hey, I was looking for the PK2 format, i found this link, http://www.stealthex.org/site/showthread.php?5440-More-about-PK2-Internals, in the https://github.com/DummkopfOfHachtenduden/SilkroadDoc/wiki/JMXPACK page,

The link is broken so can you please provide any alternate link or anything that describes the format in detail?

Hey,

I saw this: 0x750E - CLIENT_AGENT_ENVIRONMENT_WEATHER_REQUEST.cs

Thats not correct. :)
This opcode is for requesting your consignment list.

This packet is normally send by the client directly after the "spawn confirmation" (0x3012).
If you are clientless you have to send this packet manually.

Response (0xB50E):

uint8 itemCount;
uint32 consignmentId
uint8 consignmentState (0 = registered, 1 = sold, 2 = expired)
uint32 itemModelid (see itemdata..)
uint16 quantity
uint8[2] unknown .. (maybe quantity is 4 bytes long?!)
uint64 registered price
uint64 deposit price
uint64 comission price
uint32 seconds (till 1.1.1970.. presents the expiration-date or "item will be deleted"-date if already expired!)