This is the 6th and final part in my series of blog posts on RTI RID configuration tips. Each of these tips, unless otherwise noted, works in HLA 1.3, HLA 1516-2000, or HLA Evolved. If you’re interested in learning how to make better use of your RID file, check out the previous posts in this series as well.
Part 1: RID Consistency Checking
Part 2: The Advantages of MTL
Part 3: Utilize Environment Variables
Part 4: Modularizing Your RID
Part 5: Programmatic Configuration
Make sure you know what parameters your federate is actually using
Anyone who spends any time configuring RID files is bound to make a mistake from time to time. I know I do, and a large number of the questions we get in support are configuration issues as well. Even if you think you’ve setup your RID file correctly, there are some parameters that can be overridden by the RTI Assistant or programmatically by your federate code. That means examining the RID file doesn’t always tell you exactly how a federate is configured. So how can you tell? Well, there’s a RID parameter for that, of course!