December 11, 201213 yr Hi Bill Sounds like a corrupted download so download again and it should be ok. Let me know if you still have a problem. Regards Cheryl Seems that was the problem. Although I had already downloaded a second time and tried, the 3rd time was successful. Haven't time to try it out tonight but looking forward to my early morning flight tomorrow. I hope someone soon makes a video tutorial on "cameras" - I am constantly confused by all the terms and resulting conditions - windowed etc etc. Thanks for the super fast support. Regards, Bill
December 11, 201213 yr Commercial Member Thanks for letting me know Bill. If you download the latest camera guide from our downloads page then it may be useful to go through some of the examples. Regards Cheryl
December 13, 201213 yr Cheryl, I am quite confused about renaming the TrackIr files. OpusFSX also requires renaming the SimConnect files. Again, it worked on my older rig running W7. I follow both forums at Flight1 and NaturalPoint. I don't have a concise answer regarding this problem. Here is a quote from Seth from NaturalPoint on renaming the files: "You shouldn't have to modify SimConnect to use EZdok, as far as I'm aware. I think it should be expected that modifying SimConnect might break TrackIR support, as that is how TrackIR is implemented in FSX. Because EZdok has an atypical implementation, it's a bit off of the grid in terms of the standard TrackIR support pathway. I would recommend contacting its developer for resolution on this." I will try your demo when able and see if it works. Mario Bergeron
December 13, 201213 yr Commercial Member Hi Mario Renaming the TrackIR files is the mandatory advise that comes direct from NaturalPoint so it is TrackIR that requires you to rename the manifest files otherwise it will not work. You don't have to rename SimConnect files (where to you see that). You don't have to change any key assignments either, just use the standard FSX. Try the demo and follow the instructions carefully in our Getting Started guide for Single PCs. Regards Cheryl
December 13, 201213 yr Cheryl, When I say SimConnect files, I mean the simconnect.manifest and simconnectSP2.manifest files in the NaturalPoint folder. I am not touching SimConnect in any way. In any case, I will try your demo probably this weekend and find out. Mario Bergeron
December 13, 201213 yr Commercial Member Hi Mario Those are the TrackIR manifest files that Natural Point instruct everyone to rename in order to prevent TIR from connecting to FSX directly, which of course would just cause violent stutters as two program's vied for control of the FSX view or eye point. So please follow the Getting Started Guide for Single PCs very carefully. You will also find the latest 2.70.9 beta on our website, you can install this if you want, it will hopefully replace the current release versions very soon. Regards Stephen
December 13, 201213 yr Stephen, That is correct, the manifest files are the only files I will touch according to EZdok/Opus manuals. I understand the concept of renaming the files, but don't understand why TrackIr 5.2 won't connect with FSX - RH light of the TrackIR hardware off - after they are changed. Never had any issue on the old rig running EZdok/TrackIR with Windows 7 networked to an even older rig with EFB, Plan-G etc. Now, FSX is freshly installed on its new rig with Windows 8. TrackIr 5.2 works as usual on its own. I hope installing your software will remedy this problem. It is difficult to find the culprit when dealing with mutiple software. Not only OpusFSX have been prompt and receptive to my camera woes but you also have one of the best sets of manuals out there. Kudos for you. If your software can help me focus on my flying instead of wasting my time troubleshooting, it will be a pleasure to fork out my dollars for you. Mario Bergeron
December 13, 201213 yr Commercial Member Other people have had problems with the latest 5.2 driver and used the previous one. Of course the driver has to connect to the Natuaral Point SDK supplied to us by the TrackIR people. But also follow our guide and make sure you have updated your Game List in TIR and restarted it. The NP SDK will not connect to TIR unless OpusFSX is listed in its Game List. Also why not go on our Flight1 forum you will find plenty of info relating to TIR. But not sure you should bother with 5.2, others haven't. Regards Stephen
December 13, 201213 yr Stephen, Believe me, I have been posting on other forums... NaturalPoint, Flight1. They are probably starting to get annoyed. But yes, I have always updated my games on TIR, restarted, etc. Maybe an older driver will do. Mario Bergeron
December 13, 201213 yr Commercial Member You will find plenty of chat on our official Flight1 Support forum. That's where people have reported problems using the 5.2 driver. Stephen
Create an account or sign in to comment