TrackIR Settings
Printed From: SimForums.com
Category: Flight One Partner Forums
Forum Name: Opus Software
Forum Description: Support for OpusFSX for Microsoft Flight Simulator X and Lockheed Martin Prepar3D.
URL: https://www.simforums.com/forums/forum_posts.asp?TID=43026
Printed Date: September-22-2023 at 5:00am
Software Version: Web Wiz Forums 12.06 - https://www.webwizforums.com
Topic: TrackIR Settings
Posted By: Opus Software
Subject: TrackIR Settings
Date Posted: September-24-2012 at 2:39am
|
TrackIR Interface BEFORE using the interface you MUST 'Check For Game Updates' within your TrackIR5 and ensure OpusFSX is listed in Titles under the Advanced Settings tab, then restart TrackIR. Prior to using the TrackIR5 device via OpusFSX you must ensure TrackIR5 does not directly connect to the FSX/P3D simulator. To accomplish this you MUST rename the two SimConnect manifest files within the TrackIR5 installation folder. The folder is usually located in either, c:\Program Files\NaturalPoint\TrackIR5 (Win 7 32-bit) BEFORE using the OpusFSX TrackIR5 interface you MUST rename the two manifest files, simconnect.manifest and simconnectSP2.manifest. We recommend renaming these files to simconnect_RENAMED.manifest and simconnectSP2_RENAMED.manifest. If you wish to revert back to using TrackIR without the OpusFSX interface then you will have to change these files back to their original names. Check your TIR manifest files after any TIR update, the TIR software can create new files after the upgrade. Do not copy SimConnect.dll to your root directory otherwise TrackIR will find it and connect directly to FSX instead of OpusFSX. Run TrackIR and FSX before running OpusFSX. Minimise the TrackIR program to prevent FPS loss. Ensure you have no other software packages running that create camera shake effects. Do not run any other program which controls the camera views or interfaces to TrackIR. Make sure no such program or subordinate task is running, do not allow any other program to connect to TrackIR prior to OpusFSX. TrackIR Tuning TrackIR effects must be tuned using the TrackIR program. TrackIR can be used with the default TrackClip, or it can be used with TrackClipPro. TrackClipPro has its own LED emitters and its setup is very different from TrackClip, refer to the TrackClip and TrackClipPro sections below. Make sure you have Video Processing Mode set to Precision or Standard with a Precision Mode Smoothing of 100. It has been brought to our attention that on some systems TrackIR can become very jerky if 'precision' is disabled, its default key assignment is F7 so it's possible to inadvertently change its setting if you use F7 to increase flaps. TrackClip We would advise initially setting the Speed to 1 and the Smoothness to 50. You should experiment on your system and set values your PC is happy with to avoid any jerky DHM movements. Use the test options within the DHM dialog to see what the DHM should look like on your system, then try taxiing up and down in windowed mode and adjust your TrackIR smoothness to give you the optimum effect. Make sure your Light Filter Threshold isn't set too high, try setting 70, and adjusting from there, with a max setting of 12 for your IR Brightness. Light pollution and an incorrect Light Filter Threshold setting are the number one main causes of flicker. TrackClipPro It has been reported (thanks Barry and Neil) that for TrackClipPro the Camera IR brightness should be zero and Light Filter Threshold should be set to a high value. The easiest way to get the correct settings is to click the TrackClipPro button in the TrackIR window and it will reset the Camera settings automatically. Troubleshooting TrackIR Flickering or Erratic Movement Problems arise when the light threshold is wrong. If it is too low, extraneous lightsources in the room will falsely trigger TIR into seeing that other lightsource as one of the TrackClipPro's beams. This causes all kinds of false head-rotation issues, which show up as flickering. The easiest way to solve the problem is to go into the TrackIR main view, right-click on the head-graph window, and choose Camera View, and then tweak the Light Threshold to a point where there is NO red 'false lightsources' visible anywhere during the full range of head movement. This can even change during the course of a day (depending on the intensity of reflected light from windows, eye glasses, items in the room etc.). Your IR brightness levels should be zero. Try selecting the old Trackclip momentarily and then re-select TrackClipPro, and this should clear the IR settings back to zero (off). The TrackClipPro does NOT require the camera to send out IR signals (which are normally reflected off the front of the old Trackclip for the camera to pick up). Instead, the TrackClipPro generates its own light beams directly (that's why it's connected by wire and powered) - but of course, the camera can still get confused if there are large alternate light sources in the room competing with it. Here is a handy little tip for fixing TrackIR jerkiness (reported by fiftysix), http://airdailyx.blogspot.co.uk/2012/09/spf100-track-ir-adx-tutorial.html" rel="nofollow - http://airdailyx.blogspot.co.uk/2012/09/spf100-track-ir-adx-tutorial.html Make sure you don't have any monitoring programs (e.g. FSUIPC autosave) running since they can cause TrackIR to become jerky. Try enabling the Run TrackIR High Priority option in the Server Configuration dialog if TrackIR is not operating smoothly. You may need to try different versions of the TrackIR drivers to get it working smoothly on your system. TrackIR will not Connect to OpusFSX If you update the TrackIR software remember to rename the two SimConnect manifest files within the TrackIR5 installation folder. Search your system and make sure there are no more manifest files located anywhere. Check your root directory and in fact search the entire PC for them. If TIR finds any manifest file it will not attempt to connect to Opus or anything else apart from the sim direct. Try running everything manually and don't use any automated method. Run TrackIR manually after FSX, then finally run FSXSERVER, in other words do not run TrackIR and FSXSERVER automatically via FSX or FSUIPC. OpusFSX TrackIR Settings Within OpusFSX set the TrackIR scan speed to 25 initially, the XYZ scaling to 1 and PBY scaling to 0.75. These can be adjusted on the fly from within the Configuration dialog. The TrackIR scan speed can be altered from 1ms to 60ms. If TrackIR is
jerky then adjust this setting (try 25-30) in conjunction with your TIR device
Speed and Smoothness settings to reach an optimum effect. If you set the scan
rate too high it stutters, if you set it too low it jumps.
The PBY setting should be adjusted in conjunction with the TIR device speed settings to determine the range of head movement and how far you can see behind you. The TrackIR interface can be toggled on/off within the Cameras dialog (Toggle TrackIR On/Off button), allowing camera configuration and editing with the TrackIR device either on or off. TrackIR
Operation TrackIR can be enabled or disabled for each camera view within Live Camera, this is useful for instance when you want to adjust the GPS via a small click spot, if TrackIR (and DHM) movement is frozen you can operate the click spot no matter how unsteady your head is. The TrackIR interface can be
toggled on/off within the Cameras dialog (Toggle TrackIR On/Off button),
allowing camera configuration and editing with the TrackIR device either
on or off. TrackIR Cockpit Limits To set up http://www.opussoftware.co.uk/opusfsi/opusfsx_live_camera3.htm" rel="nofollow - TrackIR cockpit limits refer to the OpusFSX_Live_Camera guide. N.B. Check your TIR manifest files after any TIR update, the TIR software can create new files after the upgrade which you will need to rename again (see above for details). |
Replies:
Posted By: Opus Software
Date Posted: October-13-2012 at 11:56am
|
TrackIR 4 Users ... Download and try the Natural Point 4.2.039 beta 1 driver. Apparently the version 5 driver does not give a smooth operation through our interface with the supplied NP SDK. http://www.naturalpoint.com/trackir/06-support/support-download-software-and-manuals.html Stephen |
Posted By: Opus Software
Date Posted: October-13-2012 at 12:02pm
|
TrackIR 5 Users ... Cheryl reports with TrackIR 5 she had to revert back to a previous driver (version 5.0.300), to get the TIR device to work correctly on our older desktop. But the TIR device wouldn't work smoothly at all, jumping all over the place with current driver. Stephen |
Posted By: SkipperMac
Date Posted: October-13-2012 at 12:46pm
Any further info on this would be useful as my TrackIR is useless today - constantly flicks back to the start point for the camera for seemingly only 1 frame, but once or twice per second at worst. I haven't updated the TrackIR driver (unless it has done it behind my back), but 2.27 is unworkable just now. Curiously, it worked last night immediately after installing the beta...  EDIT: Just checked my TrackIR 5 driver - 2.50.0.0 dated 16/11/2009 which Windows reckons is up to date?
|
Opus Software wrote:Posted By: RCFlyer51
Date Posted: October-13-2012 at 7:29pm
My TkIR was jumpy after loading 2.27, but, when I reduced the scan speed to 12 ms it smoothed right out. I believe 2.27 defaults to 18 ms each time you start it. If you readjust the scan speed after you start 2.27 I believe your TkIr will work well. I haven't found a way to make 2.27 save the 12 ms scan speed at this point. Danny
|
Posted By: vonduck
Date Posted: October-14-2012 at 1:45am
|
Unfortunately after installing the 2.27 beta my TrackIR 5 does not work at all! I need to keep the latest driver as it is compatable with P3D Is there going to be a fix for this soon? Cheers Doug |
Posted By: Opus Software
Date Posted: October-14-2012 at 2:42am
|
First ... Nothing changed in 2.27, nothing at all to affect the TIR device. Second ... The TIR interface simply reads the TIR raw data at your specified rate, scales the raw data, and sends it on to FSX via SimConnect. That is all ! If your TIR is jumping all over the place then open the TIR window and check what it is doing there. Close your curtains to prevent light polution. Get the right TIR driver installed. etc. On my main PC and laptop I had to install the very latest driver. On our lower performance PC we HAD to install the older driver (otherwise TIR was very erratic ... it did not interface to its OWN SDK correctly). People using TIR 4 have had to install driver version 4, others version 5. This is not my device I am just using the SDK sent to me from Natural Point and sometimes the TIR device wont even connect through its OWN SDK - nothing I can do about this. But I have it working flawlessly on three very different systems here, including a laptop and an old slow PC. Many others report flawless smooth operation with TIR5 and TIR4 but many had to tweak the settings and get the right NP driver. Once more ... I did not change anything in 2.27 ... and the TIR interface just relays what TIR sends to it, it does not make data up, just scales and relays the data sent from the device !!! Stephen
|
Posted By: vonduck
Date Posted: October-14-2012 at 2:50am
|
Thanks Stephen, I'll install the earlier TIR driver and see what it does... after all, the latest driver form TIR is still a beta :) Thanks for the reply and awesome product! Regards Doug |
Posted By: FoolCryptic
Date Posted: October-14-2012 at 4:10am
|
Hi Doug, My only problems with TIR were when i used it in conjunction with DHM. i was getting the spikes and overall jerkiness as if the two were fighting to centre themselves. A little messing around with the scan speed, XYZ and PBY settings soon brought that under control. At present i have a scan speed of 36ms, with both XYZ and PBY at 0.50 and it's working very well. Stephen |
Posted By: SkipperMac
Date Posted: October-14-2012 at 4:16am
Ok, this is helpful to know, although everything is working fine in the TIR window and in FSX without Opus. I'll try it again later today when I get the chance and see if I can tweak some of the settings to make it useable again. ------------- SkipperMac aka Norman i7 2600k @ 3.5GHz | Asus P8P67Pro | 8GB DDR3 RAM | nVidia 9800GTX+ 512 MB | 2 x 500GB Samsung SpinPoint F3 HDD |
Posted By: Opus Software
Date Posted: October-14-2012 at 4:23am
|
You could also try changing your driver. It can only be either the raw data being fed through the NP SDK or problems with your SimConnect updates. Stephen
|
Posted By: SkipperMac
Date Posted: October-14-2012 at 4:39am
TIR scan set to 12ms and everything's hunky-dorey!  ... except that I'm late for work lolMany thanks for everything you're doing, Stephen and Cheryl  ------------- SkipperMac aka Norman i7 2600k @ 3.5GHz | Asus P8P67Pro | 8GB DDR3 RAM | nVidia 9800GTX+ 512 MB | 2 x 500GB Samsung SpinPoint F3 HDD |
Posted By: Harpic
Date Posted: October-14-2012 at 4:13pm
|
I have reverted back to the last TIR stable driver (5.1.300), and now with Beta 2.28 TrackIR works perfectly. I don't know if latest beta driver from NaturalPoint (5.2.0) is the problem with the jumps and initial setup. There is a problem with the configure window, not saving the TrackIR settings. In each startup always reverts back to 18 ms. This issue was also present in Beta 2.27. Regards, Harpic |
Posted By: Petermuc3
Date Posted: October-14-2012 at 5:02pm
|
First update today from 2.24 to 2.28 and TrackIR shows eratic moves; it was very smooth with 2.24. I did not change anything speed=0.5, smooth=35, enabled DHM. Will try with different settings and TIR drivers, but something in respect to the TrackIR must have changed. Peter |
Posted By: vonduck
Date Posted: October-14-2012 at 9:46pm
|
I did some experiemnting today and all seems to work fione now...both TrackIR updated software (5.2) and the beta 2.28 update.. Like a drongo, every time i installed the TrackIR software it added 2 new simconnect entries in the Natural Point folder... my original two were there and dutifully renamed but of course the new entries were causing havoc as i hadn't renamed them!!! .. once renamed TrackIR worked fine... So i installed Opus (my original copy) and TrackIR with the new update.. it worked... as it had done originally... Then i installed the updated 2.28 Opus and found some frittering... i then adjusted my settings in Opus to Scan Speed 12 or 18... XYZ - 0.50...PBY - 0.50 My TrackIR settings are - Seth's Flight Speed - 1...Smooth - 50 With this setting it works well and does not jerk all over the place....  Hope that helps! Doug |
Posted By: Opus Software
Date Posted: October-15-2012 at 2:53am
|
I have corrected the problem with saving the Configuration data and also added some optional arguments to the FSXTRACKIR program to allow users to see what raw data is being received and to disable the minimum raw data limits. These changes will be posted in the next beta update. Stephen
|
Posted By: Petermuc3
Date Posted: October-15-2012 at 5:08am
|
Having TrackIR4 I tried with softwareversion 4 but this made it even worse; so I reinstalled TrackIR software 5 and tried Doug's sugestions. It got a bit better but still quite some iitters. I also noticed being on the ground with a/c not moving I have no problem to look around change views, but when I start to taxi the jittering begins. Peter |
Posted By: Opus Software
Date Posted: October-15-2012 at 5:24am
|
Are you seeing the DHM camera shake or is your system just not coping. The new beta will allow you to run the interface and monitor the TIR data just in case the TIR4 device is providing different raw data to the TIR5 device, but again, all the interface does is read the TIR raw data at the specified scan rate, scale it and send it to FSX via SimConnect. Nothing more than that. You could try running the new beta version with the TEST and NOLIMIT arguments specified. Stephen
|
Posted By: Opus Software
Date Posted: October-15-2012 at 7:20am
|
The new beta 2.28.1 has been posted. If you are experiencing problems with TrackIR you may like to try stopping the FSXTRACKIR program and running it with TEST and NOLIMIT arguments. For example, create a desktop shortcut and change the target properties to, c:\OpusFSX\FSXTRACKIR.EXE TEST NOLIMIT The TEST argument will display the raw XYZ and PBY data values. You should be able to see the Yaw angle changing through -180 to 180 degrees as you rotate your head around. The NOLIMIT argument disables the mimimum raw data limit. If your FSX SimConnect interface is struggling to cope then I would expect the NOLIMIT should make the stutter worse, but you can try out the new program arguments. Regards Stephen |
Posted By: Petermuc3
Date Posted: October-15-2012 at 8:51am
|
Stephen, I reinstalled Opus, then installed Beta 2.28.1 no change. As soon as start to move the a/c I get eratic movements. And yes DHM is working on my PC i7 920 3Ghz, nVidia GTX460. Not sure how to do your above sugestion. Thanks Peter So, back to 2.24 and no jitters. Too bad I cannot use the new features. But I am sure you eventually get the things sorted out. Again thanks for your support; it is nevertheless a great product. |
Posted By: Opus Software
Date Posted: October-15-2012 at 9:46am
|
Create a shortcut on your desktop for the FSXTRACKIR program and edit its properties. Try the suggestions above. That's all I can do for the moment. Nothing changed much since 2.24 just tweaks to the settings you can now adjust in Configuration, plus possible NOLIMIT imposed. There really is nothing else to change because the interface is quite straight forward. If NOLIMIT works best with other settings then I will provide a means to add parameters to the interface program by running it via a batch procedure. Stephen. You are going to have to edit your Configuration and Weather settings again since the software is not designed to be forward compatible, not possible. |
Posted By: Opus Software
Date Posted: October-15-2012 at 9:50am
|
The only thing I cannot test is TIR 4 since I have 5. What version of TIR driver are you using? Stephen |
Posted By: Petermuc3
Date Posted: October-15-2012 at 10:40am
|
Thanks Stephen, I will try that. TIR4 with TIR5 driver; I tried TIR4 driver, made it even worse. It is really strange that everything is runing smooth with 2.24. Peter |
Posted By: Opus Software
Date Posted: October-15-2012 at 10:59am
|
2.24 just had either a 10 or 20ms scan rate but may not have had any limits applied and used 1.25 scale factors. Try NOLIMIT option with the above settings and everything will be the same. Stephen |
Posted By: Petermuc3
Date Posted: October-15-2012 at 1:46pm
|
No luck, I tried as adviced but no luck. As non native English speaker it's a bit hard to describe, but in the VC with TIR enabled it looks like the cockpit is shaking up and down extremely fast (no, not the DHM, looks different, runs parallel) then it behaves normal and the faster the a/c the scittering comes more often. I tried with PMDG NGX and QW Avro. So at least on my computer there must be a difference between 2.24 and 2.28 in handling TIR. Maybe it has to do with the set of views for one aircraft only one (VC left seat) with TIR enabled. Peter |
Posted By: Harpic
Date Posted: October-15-2012 at 1:56pm
|
Beta 2.28.1 works well in my system, with 5.1.300 driver for TIR 4. I only have one VC camera configured, asigned to about one hundred aircrafts. Now I'll create more cameras to see if the problem is asociated with having too many cameras. Harpic |
Posted By: Harpic
Date Posted: October-15-2012 at 3:16pm
|
I have created 7 cameras assigned to multiple aircrafts, with different joystick buttons. No problems at the moment. The views are smooth with 18 ms and DHM effects on, and there isn't any problem at the load of the TIR interface. I only have installed latest stable drivers (not beta drivers) from Naturalpoint (5.1.300). Using TrackIR 4, with a smooth of 25 and a speed of 1.3. Harpic |
Posted By: Opus Software
Date Posted: October-15-2012 at 3:25pm
| Thanks for the feedback |
Posted By: Bees Knees
Date Posted: October-15-2012 at 4:00pm
|
Using latest Beta (2.28.1) Trackir 4 with latest stable Trackir version 5 drivers (not Beta) Have been through the whole range of Trackir drivers from Ver 4 to 5. Cannot manage to slow Trackir down when panning. Reducing speed settings in Trackir interface results in losing range of movement, when compensating for reduced speed settings with increased xyz/pby setting within Opus range of movement is regained but so is the manic speed with which Trackir wants to pan. Bryan. |
Posted By: Opus Software
Date Posted: October-15-2012 at 4:25pm
| Thanks Bryan. I think you need to load and save a smooth or slow profile within TIR, you cannot do it by adjusting the scale or speed factors alone. |
Posted By: SkipperMac
Date Posted: October-15-2012 at 5:26pm
|
Beta 2.28.1 is working perfectly for me using TrackIR 5.1.300 Have another cup of tea Stephen and Cheryl Norman
------------- SkipperMac aka Norman i7 2600k @ 3.5GHz | Asus P8P67Pro | 8GB DDR3 RAM | nVidia 9800GTX+ 512 MB | 2 x 500GB Samsung SpinPoint F3 HDD |
Posted By: Bees Knees
Date Posted: October-15-2012 at 5:36pm
Oh trust me, I have tried every single profile imaginable I have adjusted curves....speed settings...smooth settings till I could do it with my eyes shut. Maybe you could attach a copy of your Trackir profile so I could try that please. Bryan. |
Posted By: Opus Software
Date Posted: October-16-2012 at 2:58am
|
Hi Bryan With TrackIR disabled is your system able to render the Smooth Camera Transitions between camera views without any stutter, or show a smooth AHM movement again without any stutter. Try Smooth Camera Transition setting right up to 100 the max and make sure everything is smooth. Assuming the drivers are OK then I have a sneaking suspicion your system will not be able to show a smooth camera transition or AHM motion since FSX simply cannot cope or process the 6DOF updates smoothly enough. Stephen
|
Posted By: Petermuc3
Date Posted: October-16-2012 at 9:31am
|
I updated my nvidianspector to 1.9.9.6 and reinstalled TrackIR driver 5.1.3 and it's going much better; still some eratic movements from time to time. My invidiainspector is set as per PMDG recomendation and I use REXE and shade for textures, maybe there is something there to be tweaked but I am not proficiant enough to do that. By the way I tested camera transition at 100 and 64; very smooth but nearly no difference in time. Also no difference when I us FSXTRACKIR NOLIMIT. I am not totally happy but happier. Any help would still be appreciated. Peter |
Posted By: Opus Software
Date Posted: October-16-2012 at 9:46am
|
There will be very little difference between 64 and 100 with PMDG. It is as I expected, the transition speed and smoothness is all to do with FSXs ability to process the 6DOF requests, the PMDG aircraft sim removes much of the processing from FSX, as opposed to other aircraft sims, leaving more time for FSX to process the requests and resulting in a smoother and faster transition between camera views. I am not sure there is much else I can do, the FSXTRACKIR prog has a very simple function, read TIR raw data at the specified scan rate, scale it and send it to FSX via 6DOF requests. Is the TIR smoother with a 6ms scan time or with something like 20 or 40ms? Stephen |
Posted By: Opus Software
Date Posted: October-16-2012 at 9:54am
|
Hi Peter I will modify the next beta to allow the scan time to be adjusted all the way down to 1ms, just in case if it is better at 6ms. Stephen |
Posted By: Petermuc3
Date Posted: October-16-2012 at 10:00am
|
Last test was done with QW Avro; I use the PMDG recommended settings for nvidiainspector for all a/cs. Hard to notice the difference between 6 and 20ms scan time. I need to try that again. But somehow there must be a difference between 2.24 and 2.28.1 on how TIR is handled on my computer. All settings the same 2.24 smooth, 2.28.1 smoot with eratic movements from time to time. Peter |
Posted By: Opus Software
Date Posted: October-16-2012 at 10:18am
|
It may be a faster scan time. Wait until next beta and try setting 1ms. Stephen |
Posted By: Opus Software
Date Posted: October-16-2012 at 10:23am
|
I will see about posting a new beta within the hour for you to try. Stephen |
Posted By: Opus Software
Date Posted: October-16-2012 at 10:48am
|
OK beta version 2.28.2 posted, with a bit of luck a 1ms scan time will suit your TIR4 device, hopefully it has been overwriting the raw data before I can scan it. Fingers crossed. Stephen
|
Posted By: Harpic
Date Posted: October-16-2012 at 10:50am
|
After some additional tests, I have found some erratic movements when using "turbulent motion" and "vibration" effects from DHM menu. If I disable such items, the jumps disappear. For me, the problem is when using some DHM effects, not TIR interface. Without effects, TIR is absolutely smooth. My hardware is capable to move Prepar3D at a reasonable FPS (locked at 30) I have used 18, 16 and 14 ms. All of them have the same problem. Harpic |
Posted By: Opus Software
Date Posted: October-16-2012 at 10:58am
|
But the turbulence is supposed to produce bumps. Please try beta 2.28.2 anyway.You can test the turbulent motions and vibration effects in the dialog. These are of course superimposed on the TrackIR head movement.Only disable your turbulence and vibration effects if they are causing problems, you should be able to see what the effects are like by ticking the Test checkboxes in the dialog. Hopefully you will see the same effects when you hold your head still in flight (if there is turbulence that is), if the effects look the same then you should leave them enabled and enjoy the RW experience. Stephen
|
Posted By: Petermuc3
Date Posted: October-16-2012 at 11:11am
|
I am almost there, set scan speed to 30, got quite some improvement. Still 2.28.1 Thanks Peter |
Posted By: FoolCryptic
Date Posted: October-16-2012 at 11:31am
|
I also found the 'spikes' reduced the higher i set the scan rate and completely disappeared at 36ms with TIR 4. Lower setting were jumping with DHM active. Stephen |
Posted By: Bees Knees
Date Posted: October-16-2012 at 1:01pm
Test 1 Smooth Camera Transitions: 4 new cameras created for testing purposes, all 4 cameras set to 100% camera transition speed. Cycling between cameras results in smooth transitions. My personal preference would be to see slower transition speeds but that is not the point here. Test 2 AHM movements: Tested using default AHM settings with Enable Smooth Head Movements ticked, some stuttering is evident but for what it's worth frame rate remains steady at 30fps where it is locked. Bryan. |
Posted By: Opus Software
Date Posted: October-16-2012 at 1:13pm
|
Cheers Bryan I assume the fast transition speed is for the PMDG aircraft, I will see about extending the range again. Stephen |
Posted By: Michael2
Date Posted: October-16-2012 at 2:02pm
| I have this occasional jerkiness or spiking as well. How do I adjust the scan time? I can't figure out where to access that setting. |
Posted By: Opus Software
Date Posted: October-16-2012 at 2:09pm
| The scan time is in the Configuration dialog. |
Posted By: Petermuc3
Date Posted: October-16-2012 at 4:03pm
|
I adjusted the scan time to 36 and now. I love it. Peter |
Posted By: Michael2
Date Posted: October-16-2012 at 4:32pm
| Thanks for the reply -- I adjusted it to 28 and the problem appears to be gone. I'll have to give it a real work out tonight to make sure. |
Posted By: kevinfirth
Date Posted: October-17-2012 at 3:09am
|
Sounds like you've fixed the problem here by allowing users to adjust the settings to suit their particular system in every conceivable way....now, about those winds aloft?? Gribble gribble!! Well done! K
|
Posted By: Opus Software
Date Posted: October-17-2012 at 3:46am
|
Historic data ready next week, True winds aloft will be ready in two to three weeks, along with weather smoothing (a first for the industry). Regards Stephen |
Posted By: Michael2
Date Posted: October-17-2012 at 2:11pm
|
Well, I spoke too soon. The jerking or flicker still happens with the scan speed set to 28, although it seems improved to a tolerable frequency. Stephen, are you seeing this at your end? When, and only when, DMH becomes active during ground roll or turbulence, I get an occasional jerk in the otherwise smooth shaking. It's as if the view is significantly displaced for only a single frame. The effect is like a flash or flicker. I would like to know if this is something definitely related to the scan rate and whether I should be going up or down from the default, which I guess is 12, to try and end the problem. (I should add that in spite of this issue, this is among the best software I have ever purchased for FSX - it really has tansformed the experience for me.)
|
Posted By: Opus Software
Date Posted: October-17-2012 at 2:47pm
|
I will check out the DHM with TrackIR with your settings tomorrow. There should be any spikes getting through since the DHM software is not aware of wether it is feeding data direct to the sim or via the TIR interface. It's more likely to be that when DHM is active the TIR interface has to update SimConnect more frequently, the two data sources being combined. I will check it out tomorrow though, but we haven't noticed any jerky action at all up to now. I mostly use a setting of 18ms. Regards Stephen |
Posted By: feebee
Date Posted: October-18-2012 at 4:57pm
|
I am using Track IR 4 hardware with V5.1.3 software. What profile in TrackIR do I use? Do I need to set anything in the TrackIR software before using the livecam function? These may have been answered in these threads but I can't see anything specific. thanks Graham |
Posted By: Opus Software
Date Posted: October-18-2012 at 5:19pm
|
Use whatever profile suits you the best, most opt for a smooth camera movement with or without dead zone in the centre. You should also adjust the TIR Speed and Smoothness settings to give you the smoothest response to head movement. You could try settings of 1 and 50 then adjust from there. You can alter our scan time and scaling factors again to suit the smoothness of motion and the required total head movement, just enough scaling to see behind you should do. You may find the defaults perfectly fine. But the Live Camera software does not require any specific settings in TIR. Stephen |
Posted By: feebee
Date Posted: October-19-2012 at 4:09pm
|
Ah well. I have tried to get TrackIR to stop juddering but I give up for now. I have disabled all cams and gone back to EZCA. I now only use the weather engine part which is what I wanted anyway and well worth the price just for that! I will revisit the cam side of things after xmas when more features etc are added. Graham |
Posted By: griphos
Date Posted: October-20-2012 at 3:11pm
|
I have the same issue. I have it smooth enough (10) and it moves at a speed I am comfortable with (.6), but fairly often, it just jumps a bit for no reason. Not sure what causes this in the interaction between Live Camera and TIR. Didn't happen in EZCA. On the other hand, I like the smoothness and speed better than my old experience with EZCA. I didn't try these settings there though. The DHM is fantastic, and I can now have TIR enabled when setting up cameras, so that's much appreciated! |
Posted By: SkipperMac
Date Posted: October-20-2012 at 3:28pm
|
Try fiddling with the scan rate within Opus. My TIR was "jumping" as well, seeming to flick back momentarily to the default "dead ahead" position for that camera. I adjusted the scan rate slightly and it totally fixed the problem. ------------- SkipperMac aka Norman i7 2600k @ 3.5GHz | Asus P8P67Pro | 8GB DDR3 RAM | nVidia 9800GTX+ 512 MB | 2 x 500GB Samsung SpinPoint F3 HDD |
Posted By: Michael2
Date Posted: October-23-2012 at 10:28am
| I adjusted the scan speed to 32 and haven't had a single judder for several flights. |
Posted By: Opus Software
Date Posted: October-23-2012 at 11:00am
|
We have found that it is very easy to go too fast for FSX to cope, under such circumstances FSX seems to throw away the 6DOF requests until it can once again cope, hence some of the stuttering. We are now experiencing some of these issues with LC control and having to slow things down a touch so that everything remains in sync. Stephen
|
Posted By: griphos
Date Posted: November-02-2012 at 11:27pm
|
I haven't been installing the betas. I had TrackIR working nicely with the last full version (1.24 I believe). I installed the new version and had to readjust things again in the TrackIR profiles, changing the curves so that I had good range of movement again. Except I don't have full range. I was able to look 180 degrees behind me before. I've changed the curves so that I can get close to that now, but only to about 160 degrees. In the TrackIR window, I have full movement beyond 180 degrees, but not in FSX with Opus running. I have tried changing the XYZ scaling (from 1.00 up to 2.00) but it does not change how far I can turn my head. Not sure what you changed, but it significantly changed how my profile works in FSX. |
Posted By: griphos
Date Posted: November-04-2012 at 10:31am
| I'd still like to know what settings to try to get back 180 degree range of motion. |
Posted By: Opus Software
Date Posted: November-04-2012 at 10:42am
|
The scaling in the Configure dialog should do it in conjunction with the TrackIR speed and smoothness settings. The TIR data is just raw data values so any changes will effect the settings. Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 10:50am
| Hmmm...that's not my experience. I have changed the XYZ scaling from 1.00 through to 2.00 without any change in the final degree of movement. It always stops at about 160 degrees. As I said, it didn't used to until I upgraded to the latest version, so something must have changed. |
Posted By: Opus Software
Date Posted: November-04-2012 at 10:53am
|
I said the scaling should be adjusted in conjunction with the TIR speed and smoothness settings. I would put the scaling back to its defaults again and set up your TIR profile, speed and smoothness. Then adjust the scaling if needed. Remember the scaling is just applied to the raw data it receives from the device, so you should adjust the device first, then tweak the scaling as required but set the default values in first. Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 10:57am
| Yes, as I said in my first message, I have adjusted the speed and smoothness and also the profile curves (not something I've had to do with prior versions) in order to even go beyond 90 degrees. When I first tried Opus, I was unable to get TrackIR to go beyond about 100-110 degrees, if you'll recall, and something you did in one of the versions fixed that problem. I then set up speed and smoothness in TrackIR so that I could look fully behind me and had smooth movement. Then I installed the latest release version, and once again I could only look about 90-100 degrees. So I changed speed and smoothness again, without much effect. So I have to significantly alter my profile curves so that I could even get close to 180 degrees (about 160). I then tried changing the scaling, but changes there have had no effect. It was working fine, and now it's not, and I've changed nothing else, so something you've changed in the latest release version or the betas leading up to it (that I didn't install) is preventing full range of motion again. |
Posted By: Opus Software
Date Posted: November-04-2012 at 11:04am
|
What is your PBY scaling set at. I am sure I can get full range of motion here but will check again tomorrow. The scaling does nothing other than scale the raw data from the device. You should be able to adhpjust it and see a difference. I will check it again tomorrow just in case. Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 11:11am
|
I've left PBY scaling at default. I tried adjusting it a small amount, but noticed no difference, so put it back at default. I was surprised that scaling didn't seem to have an effect. Perhaps it did in some way, but not with respect to the limit of motion. If I have a chance, I'll uninstall and reinstall the 1.24 version and recheck as well. |
Posted By: Opus Software
Date Posted: November-04-2012 at 11:12am
|
Do not go back, the software is not pt backward compatible. Just adjust your PBY scaling. Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 11:17am
| Okay, I won't roll back. I'll try adjusting the scaling again and see, but I've tried already. |
Posted By: Opus Software
Date Posted: November-04-2012 at 11:21am
|
Make sure you adjust the PBY scaling in conjunction to tweaking your TIR speed setting and profile. Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 11:27am
|
AHA! So, as I said, I only adjusted the PBY scaling a little, since I thought it would be XYZ scaling that would matter. I adjusted it from .75, which was the default, to .85, and didn't notice a difference. I've just tried it again, and I noticed a slight difference (say 5 degrees further back). So I kept adjusting and, viola, that is the issue. It seems the PBY scaling sets a hard limit to how far behind one can look. At 1.00, it appears to be 180 degrees. Higher settings mean I can look more than 180 degrees behind me. I hadn't noticed a hard limit when looking around before. Is that something added since the last full release version? I kind of like it, actually, now that I know how to adjust it. It prevents the Exorcist head movement possibilities I used to have. I can still get those if I want -- a PBY setting of about 1.5 seems to allow me to pivot my head completely around and look out the front of the plane again. :-) So, I've set it to 1.00 and now have full range to behond the plane. Really makes it a lot easier when I'm flying MP, as I mostly do, and need to look behind me to see where others are at (which is usually behind me). So, what does PBY mean, anyway? XYZ I think I understand. |
Posted By: Opus Software
Date Posted: November-04-2012 at 11:32am
|
We added XYZ and PBY adjustable scaling some time back, before it was hard wired into the interface. The XYZ scaling adjusts the X (left right), Y (up down), and Z (fwd back) raw data movement of the head. The PBY scales the Pitch, Bank, and Yaw raw movement data. A setting of 1.0 means no adjustment or scaling is applied to the TIR raw data etc. Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 11:39am
|
Thanks for the explanation and the help. Just flew a circuit in the A2A Cub with the new settings and all is well! Great weather too! Bowerman appears to be SVFR at the moment! :-) I've had to adjust speed and smoothing. It appears that .5 speed and full 50 smoothing gives the best results now. I started out with 1.0 and 10, but have progressively decreased the former and increased the latter. That seems to change with each release, but I suspect we are settling in on final settings for the TrackIR interface now. And it's a matter of preference as well. I don't like my head to move too fast. |
Posted By: Opus Software
Date Posted: November-04-2012 at 11:46am
|
You are correct, the TrackIR interface has completed its round of development at present, we have tried just about everything to overcome the stutters on just the few systems experiencing them but are convinced now that the reason lies elsewhere. The only likely future upgrade will not affect the interface, it will just add adjustable limits associated with the camera views (stop the head moving outside the cockpit etc.). Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 11:52am
| That will be nice. EZDOK has such a feature, but I found it so cumbersome that I never used it. As it is now, I just have that axis with a pretty flat line so that I can't move to that side very much. I know most people don't like to mess with curves, but you really can set up TrackIR to do pretty much what you want it to do by means of them. |
Posted By: Opus Software
Date Posted: November-04-2012 at 11:55am
|
That's interesting because I do not want to waste time developing software when there is already a manufacturers method for doing that. It is not high on my list though. Stephen |
Posted By: griphos
Date Posted: November-04-2012 at 12:01pm
| Yes, I wouldn't think it should be a priority. Of course, setting up the curve in TrackIR is independent of the aircraft one is in, and so doesn't really stop me from moving outside the cockpit. The ability to adjust limits for each aircraft while setting up cameras so that one is kept in the cockpit would be very nice. But you have a lot on your plate, and I think most people can live without that feature until you have more time for it. |
Posted By: Opus Software
Date Posted: November-09-2012 at 6:16am
|
Mavrocket posted some information on another topic which may be of some help to people experiencing jerky TIR .... 1. I initially started using the v5 software from NP, but then switched to v4, this seemed to help. 2. In the TrackIR profile settings, I copied the initial "Flight" profile and added a null zone to all axes of movement. 3. In the Opus configuration window, I set the TrackIR update speed to 20ms, and the next setting below (can't remember off the top of my head what it is) to 0.50 and the XYZ setting to 0.75. With those settings and the setup, I now do not experience any TrackIR stuttering or jumping, even when my FPS dips way down into ~10 FPS range. |
Posted By: griphos
Date Posted: November-09-2012 at 8:02am
|
In item #3, setting the XYZ and the PBY settings to 0.50 and 0.75 just limit how far you can turn your head. They just scale the TIR input, according to what Stephen says above, and so shouldn't affect smoothness. A setting of 0.50 means you won't be able to look past about 90 degrees to the side. Can't speak to the other suggestions, as I don't really have jerkiness anyway. |
Posted By: J van E
Date Posted: November-09-2012 at 8:22am
Interesting. Not being able to move my head around made me move to another camera program (for the moment being). Maybe I should give Live Cam another try...
 |
Posted By: Opus Software
Date Posted: November-09-2012 at 10:59am
|
In addition to setting our acan rate and scaling factors, you must also tweak the TIR device settings, including the advanced or Camera Light Sensitivity and IR settings. The Light Sensitivity Level is supposed to be the main cause of stutter (according to email from NP). Stephen |
Posted By: J van E
Date Posted: November-09-2012 at 11:15am
|
Ok, I am back in business. I decided to give Live cam another try and to actually TEST various settings to see what they do. Well, the problem I had with not being able to look behind me was indeed due to PBY Scaling being at 0.75. Don't know if that's the default number but I set it to 1.00 and all is perfectly fine in that regard. Just run the game in windowed mode, look behind you and change that PBY number: you will see your view being limited more and more the lower you make the number. My advice: leave it at 1.00! Secondly: the huge jumps/movements of the screen were due to the Scan Speed. It's very odd but I had it at 12. I turned it up a lot and looking around got stuttery. So I turned it to 1 and with that setting I got huge jumps/movements! After setting it BACK to 12... the jumps were gone...! Odd... Maybe some setting got stuck somewhere and I had to change the setting in OpusFSX to reset it...? So... I'm good again now! It pays to actually test various things so you know what you are doing. BTW I have TrackIR 4 hardware but still use TIR 5 software. EDIT After flying with the EZCA wobbles for a few days, OpusFSX DHM looks so much better...! |
Posted By: Chunk
Date Posted: November-09-2012 at 4:10pm
|
Thanks for the heads-up on the PBY settings Griphos. I wasn't sure why I couldn't turn my head around further. The question I have is my zoom level in cockpit. When I started the sim without DHM, I was at a .80 zoom level, with DHM enabled, I get into the cockpit, and my zoom is set to .50. Any ideas why this is happening? I like the zoom at .80, and I want it to stay there. Thanks BTW, this is a great overall product!
|
Posted By: Villan
Date Posted: November-10-2012 at 1:51am
|
G'day Hi i just been trying out your program the demo one and i happen to be getting some problems myself. TIR 5 can't be used with OpusFSX open on the main panel as the VC is all over the place. If the sim is in paused state it will still jump and i can only stop it if i pause my TIR 5. Also i can get it to stop when i have the camera tab open but i cant see the shaking in side the VC and as soon as i close the camera tab its back. Every time i try and change scan speed it will go back to 12. This happens only if im going down in numbers not up so at 20 that will be saved. I would like to get the demo to run right before outlaying the $$$ Thanks Darryl
|
Posted By: J van E
Date Posted: November-10-2012 at 4:28am
Sounds like you need a higher scan speed... BTW You can't see the shaking when the camera tab is opened because that automatically pauses the game and stops ALL effects. Closing the tab unpauses everything. |
Posted By: Opus Software
Date Posted: November-10-2012 at 4:28am
|
G'day Darryl You need to set up TrackIR as per the Getting Started for Single PCs pdf. You must update your game list, rename the manifest files etc. Probably in your demo version the minimum scan speed is 12. I would recommend setting it at 25 to start with. Also set the TrackIR Speed to 1 and the
Smoothness to 50 in the TrackIR program. Ensure you have no other software packages running that are trying to control the camera or create camera shake effect. Regards Cheryl
|
Posted By: Villan
Date Posted: November-10-2012 at 7:28am
Give this a go run OpusFSX and go to cameras and look for Z-Axis just click up or down and stop to stop it. set your zoom you want from there and then Save all cameras. then shut down that tab. You may find that your camera will always say .50 but you have it at .80 PS. you can also use the other ones to move yourself around in the seat to be seated were you would like to be. left,right,up or down. Hope that helps BTW i had read about every post from avsim about your program and i think i did read if you had the older OpusFSX you got a discount for the newer one. I would like to know if i got 2.30 think thats the one out now what kind of updates would i get. As you was making lots of changes almost every day. Its still beta as well ? Thanks Darryl |
Posted By: Opus Software
Date Posted: November-10-2012 at 7:37am
|
You could also just create your VC cameras with a zoom setting of 0.8, set the captains view as tye default view and assign buttons to all of them. Then you have achieved everything you want. Stephen |
Posted By: Opus Software
Date Posted: November-10-2012 at 8:46am
|
Everyone gets free upgrades. You can try the betas, they are pretty stable, just download the zip and extract to your OpusFSX installation folder. Regards Cheryl |
Posted By: WilliamJSS
Date Posted: November-10-2012 at 4:17pm
| Is there a cockpit walls like function for Opus? So as your head movement using TrackIR stays inside the cockpit? |
Posted By: griphos
Date Posted: November-10-2012 at 10:00pm
|
You'll find some discussion of this on p. 2 of this thread. |
Posted By: Opus Software
Date Posted: November-11-2012 at 7:08am
| We will be introducing cockpit limits in the future. |
Posted By: WilliamJSS
Date Posted: November-11-2012 at 11:48am
| Thanks! |
Posted By: Opus Software
Date Posted: November-12-2012 at 5:25am
|
Possible cause of the jitters ... You do not necessarilly have to be next to an open window to cause the jitters, any nearby IR source or IR reflector will produce them. Make sure your Light Filter Threshold isn't set too high, try setting the default 100, and adjusting from there, with a max setting of 15 for your IR Brightness. Also make sure you have Video Processing Mode set to Precision with a Precision Mode Smoothing of 100. You can adjust TIR to suit from there. These recommendations come from Natural Point, light polution and an incorrect Light Filter Threshold setting are the number one main causes of flicker. Everyone needs to get into the habit of checking their TIR manifest files after any TIR update, the TIR software can create new files after the upgrade. Regards Stephen
|
Posted By: Chunk
Date Posted: November-25-2012 at 11:37pm
| I got my issues all squared away with the DHM settings, and this program is proving to be a real winner. Thanks Griphos, Villan, and Stephen! |
Posted By: Den
Date Posted: January-04-2013 at 9:23am
|
I'm new to the forum and the following may have already been addressed. In trying to adjust the smoothness of TrackIR5.2 in conjunction with the OpusFSX Camera speed indicator I've noticed that OpusFSX will not retain the readjusted slider setting after saving all camera views. I must be missing something? Lest I forget, OpusFSX is outstanding! |
Posted By: Opus Software
Date Posted: January-04-2013 at 9:25am
|
What slider ... the vertical slider in the Camera dialog is nothing to do with TIR, it just alters the speed of movement for ajusting the eye position. Stephen
|
Posted By: Den
Date Posted: January-04-2013 at 9:29am
|
Wow! Thanks for the quick response... Yes I understand that adjustment. But in my case, I'm trying to find the happy medium between what my screen is doing versus the speed of TrackIR in a effort to remove the jitters. Immediate adjustment to the slider seem to help me balance the rate of change in the view. But, when I return to the Camera settings in OpusFSX the slider has returned to it's "original" setting.
|