Le0kong

WOW! It just took them some 4 months! :D Thanks for the update. Is there some kind of change log?

Couple of things to check: - If things look ok inside Freetrack but only show the problem on DCS, then you should try setting to default the TrackIR axis on the Axis Commands in the DCS options, to make sure they haven't been changed by mistake. - On Freetrack maybe you have a different profile being detected for DCS with some options set wrong, try deleting that profile and start over.

Thanks! From another CDU chapter drop-out. :D To correct the problem of the waypoint being in the middle of the runway, what about using the OFFSET page from the CDU, using half the runway length (as offset distance) and runway heading (as bearing) to generate a second waypoint at the beginning of the runway.

I was on Windows 7 32bits but moved to 64bits because of DCS:A10C. But i'm still using the 32bit DCS binaries for Freetrack. :P

No, you just connect it with a Bluetooth adapter (if your computer don't have one already) and point it to your head just like the TrackIR camera. If you can get a Wii remote for cheap (just make sure it is a original one and not a knockoff) or already have a Wii, then it is a great cheap alternative to a TrackIR (very rare and expensive where i live). I never used a TrackIR to be able to compare with a Wiimote+Freetrack but from videos there's not much difference in what you can do, althrough TrackIR seems quite more "smooth", or maybe it's because i prefer to use as little smoothing as possible to have it snappier. Biggest problem right now is it's only compatible with 32bits DCS exe via a "fixer" (info here). If you are short on money and still saving to buy other things like pedals,MFD, touchscreen, etc... then i will say go with Freetrack+Wiiremote. If you have the money go with TrackIR.

Ooooh, so THAT'S what the offset page really is for. :doh: I completlly ignored this page because i through it was for something completely different (see page V-11 from JP3-09-3, offset direction on ingress to target, to separate from friendlily artillery line of fire). I feel just like the picture you posted too. :lol:

ijozic, your post gave me a idea... Why are all the volume knobs on the cockpit on max by default? Is the normal for a pilot to fly with them all at max? Won't it be better if they are all at medium by default(but maintaining the current volume level), so that we can increase them in flight?

But this is going to be a re-run... i already watched this movie :D: http://forums.eagle.ru/showthread.php?p=1111465

Another one: What does the "end of vul" that the pilot says means, when you ask for check-out from a JTAC?

From the creator of the TrackIRFixer: http://naturalpointofview.blogspot.com/p/trackirfixer.html And from ED: http://forums.eagle.ru/showthread.php?t=33510

For the first one you can use this. It's not a great solution, but is the only way i know how to do it. For the second one i'm not sure what you mean, but after you create a profile via the Profile Editor and save it(on the default Saitek folder) you need to right click the Saitek tray icon and select the profile you created from the list(the icon will become green). This needs to be done every time you start the computer.

The TrackIRFixer needs to be re-applied after the patch is installed.

What are you trying to archive? Are you trying to do something like using the Pinky button as a shift, or something more complex?

It could be easier to just use uTorrent to check(hash check) and fix the file, without re-downloading all of it again. Use the torrent file from the same page you downloaded the DCS files. Here are the steps: http://forums.eagle.ru/showthread.php?p=1165481#post1165481

Since the same problem happen in in a different computer, is more likely that the problem is in the monitor itself. At this point i recommend sending it back. If you still want to try something else. Try leaving only the screen plugged on the USB ports, to test incompatibility with some other device you may have. What OS is on your main computer? Is the netbook using the same OS?

I never used this kind of monitor, but a couple things to try. Have you tried testing it in another PC? If possible. Are you using some default drivers that auto-detected in Windows when you plug, or are you using some driver that come with the monitor?

The resolution should not be making much difference. I never tried lowering the resolution on DCS (at 1920x1080 is already not much to read the labels), but on every other game i tried it didn't make any significant difference on this card. You mentioned it is a single slot version, maybe the fan is not so good, see if temperature is not too high (i get a 70°C maximum here). Another thing is if you changed the card without a Windows reinstall maybe the drivers are causing problems, or the cached files by DCS (ex: shaders compiled). But leave that for last or if a ED tester confirms the need.

That sounds a lot like the Battlefield Commander feature that ED had to remove during the Betas. I remember that you could click on some flags on the F10 map to give attack orders for artillery and tanks, on the Betas. I never looked too much on what can be modded on DCS, but i think the problem is that you can't change units or waypoints on-the-fly during a mission.

For the vsync you need to edit the graphics.cfg file(line 22) to '1', the vsync option on DCS don't work. On take-off from Batumi i get 32 FPS(default weather, no AI), in flight with the TGP-off and above ~5000f i get between 35-60 FPS. Flying low over city's get a minimum of 20 FPS however. With the TGP on the framerate caps at 45 too. Note that i use the 32bit DCS, and the GPU is overclocked a little, but it should not make much difference. CCC version is the 11.4 preview. Attached are the settings i use.

It is a hardware problem, one that is normally addressed by other manufacturers by supplying the stick with a calibration option in the drivers. The X65F drivers don't have that, only the Beta drivers, but these remove the Force Settings making them useless, and the development of these drivers seems dead anyway. This centering problem is less visible when using high force settings too. Get a login and password from BugMeNot to enter the Saitek forum, and see the sad state from lack of support.

Off-topic, but... Agreed. Never will have imagined TechSupport to answer that question with anything other then "Please look at our website for the minimum requirements".

Sounds similar to another user topic, with the airspeed reaching 50 KIAS on a dive. http://forums.eagle.ru/showthread.php?t=69751

+1

I'm using a Wii remote and a custom clip, so i'm not what you can do. In my case now it loses track just a bit further then the point where i can't look at the screen anymore, so it's good enough. I did have a problem with the middle LED losing track once, that later i discovered as because my hair got in the way, the solution as a haircut. :D About the head position, there's a topic for changing the default for the A-10C, not sure if it's the same for BS.

Right click in any of the curves and select one of the 'Dead Zone' options. Another thing that help is increasing the Average slider in the Advanced tab, i use around 10%. Increasing makes it more smother at the cost of speed, making the head lag behind you real head.