open-dis / dis-tutorial Goto Github PK

The DIS 7 version of the PduType enum appears to be a modified copy-paste of the Dis 6 version. Though new PDU type enums have been added, the lookup array initialization is initialized on line 109 with a length corresponding to the DIS 6 version (68). When the enums with indexes beyond that are added by the static initializer on line , an index exception occurs.

Greetings and great work on this tutorial. You folks are doing a great job of fulfilling the need for information on DIS for those of us involved in M&S.

Would it be worth putting in a section or a reference on how to build a rudimentary DIS test bed? I'm to the point where the way I'm going to learn is by seeing DIS PDUs flowing around a network, but I don't know where to start.

I know this is a little vague, but I'm looking for a jumping off point to building basic DIS models and pass PDUs around a network, and the tutorial might be a good place for a reference to this.

I am looking to generate the documentation in the tutorial folder, and the pandoc_MD_order.txt seems to call out folders/files that don't exist in the clone. For example the folders III_DIS_Messages and IV_DIS_Issues don't exist.

Please remove all references to 'he' and use 'they' (or alternative inclusive term) instead.

The table in the Dead Reckoning wiki page should read:

It looks like 3 and 4 have been duplicated (remove the dup) and the additional "DRM(F, P, W)" in 1 should be shifted down.

This project code repository was the initial source of the tutorial. Midway through development it was copied by @mcgredonps into the project wiki (https://github.com/open-dis/dis-tutorial/wiki).

The problem is that having the tutorial docs in two places causes some confusion for readers and maintainers about which is the source of the tutorial. I can only assume the docs are out of sync already.

We need to decide which to keep (code or wiki) and then turn off (or remove) the other.

It's not clear to me from the documentation how to employ wireshark correctly.

I have been working on the c++ opendis implementation, and I am trying to ascertain how to use wireshark properly. the Documentation explains what wireshark is and what it does. but the instructions for how to verify it works for a specific example I haven't found. I would be glad to add the documentation, but I don't know how to do it yet.