Jack McCoy

This was reported by at least 3 people last evening, in a MP session using version 2.2.0 (latest patch at the time), Nevada.

You nailed it: I'm using JSGME. Thanks.

DISCLAIMER: I have no formal rotor wing training. Me too. Translation is one thing, but these roll changes seem abnormal. It reminds me of a 3D matrix math error where the forces would be in world coordinates instead of the aircraft's local frame. It also feels to me, the power-change-induced yaw and roll seem to manifest themselves mutually exclusively.

Today I had the same problem involving the creation of the checksum for Nevada.surface5. I applied the same work-around with success. The new Normandy terrain, Normandy1944s.surface5, also needs to be moved outside the DCS World folder before taking the snapshot. :cry:

I'm here because I'm running low FPS at Batumi in DCS 1.5.7. Normal DCS performance is solid 45 FPS (Rift, GTX 1070 Strix, i7-7700K @ 5.2 GHz, 16Gb ram). At Batumi on two specific headings (150 mag and another North-East) the FPS drops to 8-25! I get this on different aircraft. I observed that the Mirror performance metric was usually 0.0-1.0 but 6.0-8.0 when FPS dropped. Tweaking the water setting to lower and turning off mirrors of the aircraft did not improve things. I thought it could be "end of map" related, but performance in the northern end of map is spectacular with 90 FPS on northerly headings. Mi-8 Disabling the mirrors reestablishes 45 FPS on heading 150 but not heading 40 which seem to only increase by 5-10 FPS to around 32-37 Gazelle To my knowledge it has no mirrors, so I can't disable them. It's as if the mirrors were still rendered to a render target.

I noticed this today using the Warthog and I made sure no other controllers were mapped to Pitch and Roll. I did notice the virtual cockpit stick going forward as I pulled back, but didn't investigate quite as much: just logged in here to report the bug. (I'd also like the FSX Maule ailerons to be fixed... :doh:)

VR boy here, just bought CA. Not usable without a barf bag. Quick patch suggestion? if (vr_enabled) { vr_head_azimuth *= -1; vr_head_elevation *= -1; }

I noticed that some installed stock file and folder names contained Unicode Cyrillic characters. I think they should be renamed with the equivalent Latin characters: \CoreMods\aircraft\F-5E\Liveries\F-5E-3\FI HДvllv11 (Cyrillic Д to Latin D) \dxgui\skins\skinME\images\Buttons\Piсtogram red.png (Cyrillic с to Latin c) MissionEditor\data\scripts\Enc\Weapon\FAB-100М.txt (Cyrillic M to Latin M) Mods\aircraft\F-5E\ (Cyrillic E to Latin E - not sure about this one) Mods\aircraft\F-5E\Doc\DCS F-5Е-3 _QFM_ENG.pdf (Cyrillic E to Latin E) Mods\aircraft\F-5E\Doc\DCS F-5Е-3 Flight Manual_ENG.pdf (Cyrillic E to Latin E) Mods\aircraft\Mi-8MTV2\Missions\Campaigns\ru_SpringMi8_сover.png (Cyrillic с to Latin c)

I assure you I'm well aware, but I triple-checked following your comment. :thumbup: I went back to the sim and I can reproduce the issue. I further determined that it only happens when the airplane is not moving at all: the outermost ailerons droop when either left or right brake is applied. I stand by my observations about the rudder too. The nose wheel moves proportionally to the rudder pedal input, the rudder does not. :joystick:

To me there is a bug with the rudder: any value different than zero seems to saturate 100%. It acts like Flaming Cliffs' Z and X rudder command. Also, something strange but maybe true-to-the-airplane? Left and right brake axes make the exterior ailerons move (!).

+1 :helpsmilie::doh:

+1 for the wishlist

Just bought the Mig-15. I noticed this bug, ended up here. I can't believe this would be hard to fix. It does the same on both X and Y stick axies. Looks like: Xstickmodel = ABS(Xpcstick); Ystickmodel = ABS(Ypcstick);

Fixed in version DCS 1.5.5.60314 Update 3 :thumbup: https://forums.eagle.ru/showpost.php?p=2985983&postcount=41

That only makes the blue cross disappear. The mouse values are still clipped (and/or noisy) when trying to adjust a potentiometer or other turning knob.

I just updated to version 1.5.5.59992 and it seems to have broken something. The blue cross mouse cursor is confined to a very narrow area in the center of the view frame. I tried without VR :cry: and it works as expected. With VR, when the Comm menu is open, the blue cross behaves as it should. Closing the Comm menu will exhibit the bug again. <Sorry, I might have posted this in the wrong forum>

I had to apply the registry key deletion solution twice. I can't explain why the first try didn't take.

I'm having the same problem with Mig-21Bis. I'm down to 5 activations. Or is it 4? Is it possible that the speed of the CPU be part of the CPU id key? My Asus Maximus VIII Hero is configured to operate at variable clock speeds. If some code does something like: string hardwarecode = system.getcpumodel() + system.getcpuspeed() + system.getmac() + ... and somehow the immediate value of the CPU clock speed is included in the computation of the hardware key, it could explain why the problem seems intermittent and not present on all computers.

There's no need for TARGET to use the friction slider. However, you might run into the ame issue I had: if you have many controllers connected, you might not see the Warthog-THROTTLE device. Use the scroll bar at the bottom to select the THROTTLE, select AXIS at the top of the dialog, then assign you axis. Make sure you travel all the way up and down with the slider. Good luck!

I just said that given an anti-skid system that's doing its job (not disabled under the typical behavior you mention), it would release braking to prevent skidding. It was to put in contrast that without the anti-skid, brakes locked, and near-full power, things would happen as you described below. In the end, this being a Warthog forum, my statement could be misleading. But who's to say the Sim implements the typical behavior you describe? Is this in the Flight Manual? I only read 500 of the 671 pages! :megalol: I agree and believe that. Thanks for the input.

No. With Anti-Skid, the brakes will unlock by themselves. Without A/S, when the engines supply more thrust than the static friction force, the wheels would start skidding and screeching... Not true. The brakes are designed according to the car's weight and performance expectations.

Static and kinetic friction coefficients Sorry for the necro-post, but I feel I'm getting poor braking performance with the latest patch. ED Team, do you use the static or kinetic friction coefficient? I know it should be the STATIC one for this particular situation. The static coefficient is always higher than the kinetic one, sometime by a factor of 2. With anti-skid, the maximum brake torque should be [a little less than the static coeff] x [mass on wheel] x [tire radius], or else it would be commanding to make the wheel skid. If the wheel starts skidding, the A/S needs to drop braking to below the kinetic coefficient so the wheel stops skidding. Raising the flaps is not recommended on the runway under normal operations, but not because of braking performance. I was told that the pilot risks moving the wrong ancilary control (maybe landing gear) and blocking the runway. Of course, strong winds and other factors might call for raising flaps early. As a side note, in the 172 POH, Cessna recommends to retract the flaps when applying emergency braking after an engine failure and landing on the (short) remainder of the runway.

Wait until you TIR4 dies before moving to TIR5. I have both, and they are operationaly the same. Unless you want to draw in PhotoShop using your head movement, TIR4's resolution is more than enough. As for moving around the entire cockpit, radios, etc, you have to be careful how you set your cap (headgear) on your head. I'm using a 47" monitor, about 24" from my face. With the IR camera resting on top of the monitor, it has a lookdown view of maybe 30 degrees to my head. So, when you center you TIR, make sure the reflectors are perpendicular to the camera. This will prevent insane gimble lock when looking down. Still it gets a little shifty, but plenty useable. So, I set my cap with the "flap" some 30 degrees upwards, towards the camera; so much for being stylish, but it works. Even though I'm upset at NaturalPoint for not giving me access to their SDK (f'ing jerks), I have to recommend (+10) buying TrackIR to anyone considering it. Buy it even before you buy a Thurstmaster Warthog! Ideally, the TrackIR software would ask for the physical position of the camera and remap the coordinates accordingly, but that would be a user-support nightmare for NaturalPoint, I'm sure, with people stumbling onto yet another parameter to screw up.

I pre-ordered from here: http://www.agileelectronics.ca/prod_details/tab/details.asp?prod_id=2971004 It is currently "backorder". I will let you know when they reply to my email inquiry about the replenishment date.

I'm personally developing a flight sim in which you will eventually be able to play curling and ride a Ferris wheel. No kidding. Stand by.