Earlier this week MÄK released the latest version of the RTI, 4.1. One of the big features of this release was support for IPv6. For those that don't know much about IPv6, it is the latest version of the Internet Protocol and replaces IPv4. The primary motivating factor behind the creation of IPv6 was the size of the IP address space in IPv4. IPv4 addresses are only 32 bits long. That's enough for 4,294,967,296 different addresses, but it's not enough for the size of the internet today.

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!

Having released VR-Vantage 1.4 it's time to move on to the next version. We showed several technology demonstations at IITSEC this year and we are in the process of productizing them for VR-Vanatage 1.5. 

Effects based sensors let users visualize NVG, FLIR and other sensor views without materially classifying data. While these sensor visualizations are not physically accurate, they are pretty good and since they don't require any changes to models or databases they are super easy to use. They still utilize JRM's world class technology for sensor visualization, just without the high fidelity physics based stuff (which can be enabled via a drop-in add-on module).

This is part 5 in my series of blog posts on RTI RID configuration tips. Check out the previous posts in this series, and stay tuned for more to come.

Part 1 – RID Consistency Checking 

Part 2 – The Advantages of MTL

Part 3 – Utilize Environment Variables 

Part 4 – Modularizing Your RID 

Change RID parameters programmatically in HLA 1516-2000 and HLA Evolved

The RID file isn’t the only way to specify RTI configuration parameters. Many people don’t know that RID parameters can also be specified programmatically by the federate. Unfortunately there was no mechanism for this in the HLA 1.3 API, but in 1516-2000 such a mechanism was added, and the same idea was kept in HLA Evolved (though the API for it changed). In HLA 1516-2000 and HLA Evolved, the standard included a way to pass a string or series of strings to the RTI to be used in RTI initialization. Since RTI configuration is different for every RTI, the standard left it to RTI developers to determine how these strings were used. As a result, this is one of the few areas of the API that will work differently from RTI to RTI. So if your federate needs to operate with multiple RTIs, you may want to consider other configuration options or have a switch in your code based on what RTI you are using. So how can you use these strings with the MÄK RTI?

As the news of Warren's upcoming departure from MÄK has spread after today's announcement, I've heard from a few long-time partners and customers asking for my take on what this means for MÄK. So I wanted to share a few quick thoughts. But first, this is good time to express how lucky I feel that I've had the opportunity to work for Warren for more than 18 years.

I first met Warren when I was 20 years old, when he conducted an on-campus interview at MIT. As I walked past all of the other companies' representatives wearing suits and ties, there was Warren wearing sneakers, jeans, and a T-shirt (although he did have a blazer on over the T-shirt). I said to myself "That's the guy I want to work for!" And I have enjoyed doing so ever since. Over the years, I've found Warren to be a visionary leader, an eternal optimist, a businessman of unimpeachable character, an outstanding role model, and a good friend. I wish you the best of luck, Warren, in your post-MÄK life, and I thank you for creating and cultivating a company that remains engaging, successful, and fun even after almost two decades. (continued...)

VR-Vantage 1.4 is here - bringing with it support for a new compiler MSVC++ 10 64 bit! This meant upgrading OpenSceneGraph (to version 3.0.1) and many other dependencies (Silverlining and DI-Guy for starters). Additionally a few smaller capabilities were added:

We now support HLA Evolved, allowing VR-Vantage applications to play in exercises with modular FOMs. We also added more examples and better documentation for the developer's toolkit (a trend you will see continue over the next several releases). There are also a few customer requests in here too: an object count panel, a space attach mode for attaching to satellites, an option for linear model scaling, and a way to use images for 2D symbols instead of fonts.

When preparing fo the ATCA conferences this year, we wanted to show how MÄK tools can be used in the NextGen environment.  One example we showed used the VR-Exchange protocol translator to build a bridge connecting ADS-B traffic to simulation standard protocols, such as DIS and HLA Evolved (High Level Architecture).  By creating a custom Broker for VR-Exchange using the toolkit, it allowed us to bring in live air traffic to our synthetic environment in order to visualize the traffic as well as have our simulated entities respond to the live traffic.  This is just one example of how MÄK's open toolkits allow for the products to be extended  and customized  for creating mission focused solutions.

Since this was my first tradeshow, I wasn’t quite sure what was in store for me, but it’s safe to say that in my four days on the show floor, I’ve learned quite a bit. Not only have I learned a great deal more about our company and industry, but also about my area of expertise, Battle Command – who’s using it, how they use it, and how to best and most effectively answer questions for the training classes I help teach.

For my first ever tradeshow experience, I’m surprised by how smoothly things have been going. The set-up of my Battle Command pod went well and the demos I’ve given have been positively received by customers, potential customers, and MÄK staff alike.

After another busy day on the show floor yesterday, MÄK let loose for the second night of our first ever “MÄK Fest.” We sent two busloads of MÄK staff, customers, partners, and I/ITSEC friends to Disney’s Epcot to enjoy a lakeside fireworks show, complete with dinner, drinks, hot chocolate, and the classically beautiful Disney Christmas décor.

While we enjoyed ourselves, I had the chance to speak with many different groups of customers. While the most common topic was the state of the economy, it was encouraging to hear how creative everyone is becoming to meet end-user requirements on reduced budgets. I was gratified to hear how MÄK is playing a role in meeting these challenges with our COTS products and solutions.

It’s great to be back at I/ITSEC for another year—seeing those familiar faces, a few that I haven’t seen in over 10 years, is a wonderful thing that makes being here a fun and special time.

As far as what’s happening on the show floor, I’ve seen some really innovative visual technologies around. Something that I’m sure fellow MÄK bloggers have commented on is how well our streaming terrain is being received. It seems like every time I turn around there’s a new crowd asking for a terrain demo.  I haven’t seen anything yet that is comparable to our streaming terrain…perhaps this explains our popularity.