Davee

#5

Strange, as it's there on my windows x under Eagle Dynamics.

I think that the US does not use imperial units but rather they are US measurements. Gallons are dofferent but miles are the same. Sort of a mix. In Canada, we are metric but use imperial for aviation. We have to be conversant with all three systems due to our proximity to the US and for import/export.

A dedicated server that will host at least 100 players without lag.

My understanding is that it is not yet at DCS level and also wondering about the simplicity of the startup. Will this procedure and others be moving more towards the A-10C model when receiving the DCS moniker?

F-111 Avionics and aerodynamic considerations for the developer and . . . . interesting fit for the time period.

+1

Speaking with an F-15E driver, he stated that he would have a hard time keeping up with a modern jet airliner at altitude.

I recall WAGS mentioning it verbally in one of the early streaming events.

Glad you found the fix. :thumbup:

Windows 10 FIX if TM HOTAS WARTHOG disconnects during flight. (some SIMS) Windows 10 Fix for TM HOTAS WARTHOG disconnecting. (some SIMS) Using USBDeview Program: identifies USB ports. http://www.nirsoft.net/ ID's are as follows. TM HOTAS WARTHOG connected directly to USB 2.0 Ports. Address: Joystick: Port_#0003.Hub_#0006 Throttle: Port_#0004.Hub_#0006 Your port assignments will probably differ. Using TM TARGET software ports are "logically" changed to . . . Address: Joystick: Port_#0007.Hub_#0003 Throttle: Port_#0008.Hub_#0003 Your port assignments will probably differ. Under Device Manager - a new category Thrustmaster Devices is created when TM TARGET software is started showing the above change in port numbers. I had previously gone through all my physical port settings to ensure that the box "Allow the computer to turn off this device to save power." was unchecked. However, my HOTAS would still disconnect at irregular intervals. In actuality, it was disconnecting from the "logical" ports #0007 and #0008 and reverting back to "native" port ID of #0004 and #0003 and therefore as this was happening within COD during flight, the SIM did not recognize the new settings and all controls froze. The FIX: In the Device Manager: After making sure that all the ports under Universal Serial Bus Controllers have the box for allowing the computer to turn off the device UNCHECKED - load the Target software and still in the Device Manager go to Thrustmaster Devices and UNCHECK ALL THE BOXES thereby preventing the computer from turning off the device. So far so good. NOTE: When turning off the TARGET software the ports also revert from the logical 0007/8 back to 0003/4 (DX direct connect) Summary, make sure that the USB ports under Universal Serial Bus controllers AND under Thrustmaster Devices are UNCHECKED to prevent the computer from turning them off. This may also be an issue for other Manufacturers' devices.

Target software, when activated, shows up in the Device Manager as a virtual new device under the Thrustmaster heading. Go in there and make sure that the boxes for "let the computer turn off this device to save power" is UNCHECKED. This worked for me. When the Target software is shut down, the heading Thrustmaster disappears and the TM devices now revert from virtual back to hard USB addresses under a general USB heading. (I made sure the boxes are unchecked there also in case I wanted to connect as a straight DX device in some setups.) Worked for me. Cheers,

Hat clip is no problem for looking up or high 6. There are a number of issues - for example ambient lighting that can interfere with the infrared sensor. I think you will have to play around with your settings more. Perhaps a more detailed description of why you can't look up. What are the symptoms you are experiencing? Without more information, it is hard to offer solutions. This is solveable - just gotta understand more of your settings.

Nobody is very generic. Astronomers and physicists do all the time considering what they deal with.

My understanding is that base 12 is better for navigation. Curvatures, 360 degree circles, tangents etc. They don't divide well by base 10.

No "pussy" for you!

The so called "Cobra" flown by any aircraft is a formula for instant death. It is a great show exhibit, but with another aircraft on your tail that is close enough to overshoot - you are already dead!

Been flying flanker since day one including Beta testing and my name in the flanker manual with the other testers. Got my Flanker T-Shirt as a gift. Competed in the online Ladder and still flying today. Those were the good old times of custom skins. :) Cheers, Catseye

The real F86 manual I'm looking at right now states takeoff with flaps full down and raise at 160 knots. Raising earlier will initiate a nose drop and retrimming will be required.

Variant? Need more info to compare.

Most info I'vd seen shows full flaps but I find 20% better.

IMHO it would be better to follow Cliffs of Dover example and model the damage more realistically. In that sim, the surfaces, subsurfaces - spars, cables, hydraulics, cylinder heads, glass what have you, all have values that are calculated to break when struck and the break is calculated by the type of round doing the hitting and the kinetic, thermal or AP energy of each round is calculated. There are hit boxes that contain these sub components. Angle of attack also makes a difference. In addition to the calculated damage there is a link to the appropriate graphic damage model - smoke, fire, water etc.

Thanks very much, Downloading now. Cheers

Hi All, I would really love to see the dirt overlay on the F-86 canopy made clear. The reflections are OK, but the dirt is very poor and pixelated. I've tried with my tools but I can't separate the layers. As an aside, is there a way to remove a layer via a lua file/ Thanks for any help. Cheers.

There really should be no light projection on ground surfaces during daylight hours. Only as late evening starts or very dull dark weather. Daylight is still more intense that the aircraft light beam.