File: Applications/SimpleGameClient/SimpleGameClient.ned
(no description)
The following diagram shows usage relationships between modules, networks and channels. Unresolved module (and channel) types are missing from the diagram. Click here to see the full picture.
If a module type shows up more than once, that means it has been defined in more than one NED file.
SimpleGameClient | (no description) |
Name | Direction | Description |
---|---|---|
from_udp | input | gate from the UDP layer |
from_lowerTier | input | gate from the lower tier |
from_upperTier | input | gate from the upper tier |
trace_in | input | gate for trace file commands |
to_udp | output | gate to the UDP layer |
to_lowerTier | output | gate to the lower tier |
to_upperTier | output | gate to the upper tier |
Name | Type | Description |
---|---|---|
simpleGameClient.debugOutput | bool | |
simpleGameClient.movementRate | numeric | movement updates per second |
simpleGameClient.areaDimension | numeric | movement range from [0.0, 0.0] to [areaDimension, areaDimension] |
simpleGameClient.useScenery | bool | |
simpleGameClient.movementSpeed | numeric | movement speed in m/s |
simpleGameClient.movementGenerator | string | responsible for different movement models |
simpleGameClient.groupSize | numeric | clients per group |
simpleGameClient.mtu | numeric | maximum transmission unit |
module SimpleGameClientModules gates: in: from_udp; // gate from the UDP layer in: from_lowerTier; // gate from the lower tier in: from_upperTier; // gate from the upper tier in: trace_in; // gate for trace file commands out: to_udp; // gate to the UDP layer out: to_lowerTier; // gate to the lower tier out: to_upperTier; // gate to the upper tier submodules: simpleGameClient: SimpleGameClient; display: "i=block/app"; connections nocheck: from_lowerTier --> simpleGameClient.from_lowerTier; to_lowerTier <-- simpleGameClient.to_lowerTier; trace_in --> simpleGameClient.trace_in; endmodule