Windows are controlled by a queue of events. With a bunch of things all starting up around the same time, often it's not possible to know exactly how those line up to get processed, and predict the outcome. It's up to an application to avoid taking focus away from FSX starting up, when that app shows a window.

Programs intended to be loaded with exe.xml should be aware they are started by a host and should not take focus. Something Opus should be advised about for their product. I suspect other programs may operate incorrectly started this way.

 

The guy at OPUS said his software shouldn't be to blame....  but I wonder if he knows what you're talking about too

If the Opus install puts itself to load in the exe.xml, then what I said is correct. I'm not finding fault if that's what you're trying to imply. It would be something the dev would want to know about.

The only startup in my exe.xml is couatl.

Oh ok...  The installer doesn't put OPUS in there.  But in the manual it says how to do it if you want OPUS to auto load when FSX runs.  I'll just quote your post and paste it over there because that HOST stuff is above me lol

Ok so the technicalities go over your head Ryan, but what I don't understand is why you would want to make such derogatory comments that earn you no merit.