-0303-

Example: "Clear" HOTAS binding (like JOY_BTN20 Electric Power switch A-10A). Subsequent "Default" (or rightclick "Restore combo to default") does NOT restore binding. Before making a bug report. Is this new? Could've sworn I've seen this work previously. "Restore" keyboard keys seems to work (just not HOTAS bindings). Not a priority bug, obviously.

Got (coincidentally) three catapult placements in a row. Quick and only slightly dirty fix suggests itself: If TailDragger THEN only position repairs on Catapult.

The Slip & Turn is the double needle below the VSI. It's actually much easier to see than a ball. Brakes are differential controlled by rudder. I have the pinkie button set for brakes. Works good enough for me. One person map to an analog axis on the throttle and swear by it. Seems complicated. A big help is bringing up the CONTROL INDICATORS (RCtrl + Enter) to see the brakes operating. Taxiing is an art form that can be frustrating. Once it's rolling, 1000 rpm, keep tapping the brakes and try to anticipate. Can never look away. Taking off is a matter of training again and again and again... I initially had great help by finding a Cirrus cloud to aim for to keep straight. Nose trim neutral or down one tick. This helps to keep the nose down and not stall just after takeoff. Make rudder trim with "dd" in "rudder" up. Rudder trim not important as you'll always have to counter with rudder anyway. Once you learned takeoff you can do it with any trim setting (except not having trim down/neutral makes often for a clownish takeoff). While flying you'll keep adjusting both trims with changes in RPM or speed. Spitfire may be more work than P-51D but it's a breeze compared to Bf 109 or I-16. Landing. A good setup is half the battle. If three-pointing, the touch down speed must be barely above stall speed. With excess speed it'll fly off again easily because the wings have a high AoA. Imagine tail wheel coming down last angling AoA even higher... Try to fly as low and slow as possible along the runway to land. Make sure to touch down without any sideslip as this will cause a swerve to the side. When speed is slowed down brakes are next to always needed to keep straight. ~ A tip. Elaborate but works sometimes. Make a repair on the CV. The repair routine since 2.5.6 puts tail wheel outside deck. 9 times of 10 one can pull it up with the engine but ... quite often this damages the tail wheel making it a fixed locked tail wheel. And now you can make beautiful landing roll outs without using brakes.:music_whistling:

Simplest put the algorithm treats every plane as a nose wheeled tricycle planes. Result being that the tail draggers are placed with tails outside deck or (amusingly) the tail wheel is placed in catapult hookup. See images (outside deck, tail wheel catapult hookup). End Info. Start arguing: Why should this "stunt" be indulged? - It's fun and reasonable to be able to repair at any airfield including CV. To note, the no shooting Aerobatics Server is consistently at or near the top of populated MP servers. - Historically, in improvised operations, hookless Warbirds did land on much smaller WW2 CV's. - Before 2.5.6 you could repair on CV - It's seemingly a "trivial" fix. Repair works, only problem is plane positioning. As noted, tail wheels are already tracked and treated as if they were nose wheels. I'm sure main wheels are tracked. If TailDragger THEN position = tail wheel + X meter from deck edge or sumthin'. Or if using main wheel reference then: If TailDragger THEN add tail - main wheel distance in nose-ward direction from deck edge. If I were an ED programmer it would "irk" me, it being this close --><-- to working. Trivia: Spitfire can nearly always pull itself up with minute damage, P-51D often fall off the side, I-16 gets no damage (sometimes) & Bf 109 gets severe damage. From Catapult position takeoffs are easy.

https://forums.eagle.ru/showthread.php?t=114030 I've done that a year ago, it works. Only thing the folder will retain it's name. Meaning if it's named "Open Beta" that's what it'll be after conversion.

Removed LShift R and LShift V from UI Layer. Red lines in P-51D are gone but only after game restart. Reprogramming LShift V to UI Layer does not give a warning of conflict. Red line reappear but only after game restart. Looks like there are 3 simultaneous active layers for any plane. For P-51D: -P-51D -UI Layer -General General shows two red lines "BDA show/hide" (RAlt + ') and "Chat show/hide" (LCtrl + LShift + Y). Conflict is between UI Layer & General. Plane layer (P-51D) seems to be last layer scanned. Meaning bound key function doesn't activate. Seems binding same keys between any two layers does not give a warning of conflict. Ok, what to make of that? It would be good if warning was given when binding same keys to two layers. Now, red lines will be noticed only after game restart and a guessing game of "what did I bind last?" begins. Though plane layer bind conflict would be discovered by not working.

LShift-V, that tracks. Thanks, I'll try that ... tomorrow. I'll go to sleep pretending this is the fix, so I don't get too aggravated if it doesn't work.:music_whistling: Hmmm... I've been using UI Layer LShift-R for years so this conflict must've been introduced in the TF-51D menu.

Online, yes. Not much point tweaking the server. It is only ever four preset channels. 60 airfields in Caucasus. I'd want fly, land & change crystals for next destination. Though I did try to tell Aerobatics server guys that one of the presets doesn't correspond with any airfield.

TM Warthog joystick and throttle. MFG Crosswind pedals. What I'm looking for is: Is it just me or is it everyone? Can you get rid of the red lines if you use the default bindings? I can get rid of them if I bind another key (like "H" for "Horizon Cage", instead of default LShift-V). But that's not the point. Point is, it should not be red with a clean install. Red indicates bindings are messed up in some way. Duplicated I think.

So deleted TF-51D main folder controller files. Ie everything under: ie Did DCS_Updater.exe repair again and watched them being recreated. Still getting red lines. Next step delete DCS completely and reinstall ... I don't know what else I can do?

Yes, of course. But I really don't get why I get red lines in a clean install??? That just shouldn't happen. I created yet another new Saved Games. Red lines for TF-51D Horizon Cage. Did CLEAR, exited, restarted, programmed it's default LShift-V. Got red line again??? But regardless, I should never ever see red lines with a clean install. Right? I used DCS_Updater.exe repair to make main folder "clean". Maybe this doesn't clean everything. I REALLY don't feel like a complete delete / reinstall. Maybe if I delete all controller files in main folder and then make a DCS_Updater.exe repair to reinstall only the right ones? These main folder files borrowing a picture:

In video below especially compare IAS red/yellow needle and G-meter red/yellow strip. The latter does not wash out nearly as much. How gauge colors should look? Daylight colors for comparison with night. 1920x1080 (min settings). Attached MP4 video because YouTube quality just too bad. Video: 1:00 AM night, spool engine up max Cycle "Instrument Panel Primary Light Rheostat" min - max twice Crappy YouTube, see attached Video.Zip instead. Deliberately left out Diag.txt in attached files. I'm paranoid, don't want to give out every computer detail on an open forum. logs.zip F-86 panel gauges lights.trk Video.zip

I performed an DCS_Updater.exe repair to ensure main folder is clean and deleted Saved Games. This is equivalent to a clean new install. Yet, I still get redded out lines in ADJUST CONTROLS screen. This for multiple planes like I-16, Bf109 and TF-51D & P-51D. In TF-51D it's Horizon Cage and Rear warning radar Test. Borrowing (stealing from MudSpike) an old UNRELATED image to make clear what I'm talking about. Can someone confirm? I don't feel like doing a complete reinstall to verify.

It's fixed. Now we have all four blades broken (every time it seems). Not bent, broken as in wooden propeller. Props will stop in different positions. Damage seems static, meaning prop blades damaged identically each time. Fine, it looks nice enough, way more important things to address. Note, I-16 does do different damage (both blades bent, one blade bent).

Cannot talk to ATC. Radios are preset on the ground (Server). ~ Reminds me, in WW2 ground crews switched crystals before each mission (allied and axis). Make this part of rearming / refueling menu. Suggested 7 years ago and still a good idea.

In the film The Philadelphia Experiment an invisibility device on a destroyer goes awry and becomes a time travel device. Crewmen gets melted into the deck, sticking half out ...

I've been using Naked350's mod. Until maybe 4 patches ago when Spit became readable and I took it out. Now I'll probably reinstall Spitfire Cockpit Refurb mod. ~ Note, I install Cockpit_Spitfire_LFMkIX in Saved Games here: C:\Users\username\Saved Games\DCS\Liveries and it works. Looking at instructions it says to install in the main game folder but this isn't necessary unless I'm confused. Ed/add: Looking at my own notes it's a bit more complicated. I made a unique modification so I could put it under Saved Games. I prepared Cockpit_Spitfire_LFMkIX zip file to contain Naked350's five files and a modified 'description.lua', like this: description.lua SpitfireIX-CPT_DIF.dds SpitfireIX_1_DIF.dds SpitfireIX_2_DIF.dds SpitfireIX_3_DIF.dds SpitfireIX_4_DIF.dds Original unmodified 'description.lua' copied from: C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\SpitfireLFMkIX\Liveries\Cockpit_Spitfire_LFMkIX\default In copied 'description.lua' deactivated every file (by editing out) except the five Naked350 files references. This will override the default files from main folder and instead use the Naked350 files from the Saved Games folder. Noted by trial/error that the reference to the mirror file cannot be edited out, it must remain active. Mirror file reference is the second of these two: {"pilot_RAF_FP_Notepad",0,"mfd3",true}; {"mirror_SpitfireIX", 0 ,"mirrors",true}; --mirrors texture replacement with runtime rendered one Left both these activated (not sure if first one required). I said it was complicated. All of the modified 'description.lua' (-- edits out). Note only Naked350 Refurb files + notepad & mirror files left activated: livery = { -- {"SpitfireIX_GLASS_inst", 0, "spitfireix_cpt_glass_diff", false}, -- {"SpitfireIX_GLASS_inst", 1, "spitfireix_cpt_glass_norm", false}, -- {"SpitfireIX_GLASS_inst", ROUGHNESS_METALLIC, "spitfireix_cpt_glass_diff_roughmet", false}, -- {"SpitfireIX_GLASS_inst", 14, "spitfireix_cpt_glass_diff_filtr", false}, {"SpitfireIX_3", 0, "spitfireix_3_dif", false}, -- {"SpitfireIX_3", 1, "spitfireix_nm_3", false}, -- {"SpitfireIX_3", ROUGHNESS_METALLIC, "spitfireix_3_dif_roughmet", false}, {"SpitfireIX_2", 0, "spitfireix_2_dif", false}, -- {"SpitfireIX_2", 1, "spitfireix_nm_2", false}, -- {"SpitfireIX_2", ROUGHNESS_METALLIC, "spitfireix_2_dif_roughmet", false}, -- {"SpitfireIX_GLASS", 0, "spitfireix_cpt_glass_diff", false}, -- {"SpitfireIX_GLASS", 1, "spitfireix_cpt_glass_norm", false}, -- {"SpitfireIX_GLASS", ROUGHNESS_METALLIC, "spitfireix_cpt_glass_diff_roughmet", false}, -- {"SpitfireIX_GLASS", 14, "spitfireix_cpt_glass_diff_filtr", false}, {"SpitfireIX-CPT-pribors", 0, "spitfireix-cpt_dif", false}, -- {"SpitfireIX-CPT-pribors", 1, "spitfireix-cpt-pribors_nm", false}, -- {"SpitfireIX_GLASS_ARMOR", 0, "spitfireix_cpt_glass_diff", false}, -- {"SpitfireIX_GLASS_ARMOR", 1, "spitfireix_cpt_glass_norm", false}, -- {"SpitfireIX_GLASS_ARMOR", ROUGHNESS_METALLIC, "spitfireix_cpt_glass_diff_roughmet", false}, -- {"SpitfireIX_GLASS_ARMOR", 14, "spitfireix_cpt_glass_diff_filtr", false}, {"SpitfireIX_1", 0, "spitfireix_1_dif", false}, -- {"SpitfireIX_1", ROUGHNESS_METALLIC, "spitfireix_1_dif_roughmet", false}, -- {"SpitfireIX_5", 0, "spitfireix_5_dif", false}, -- {"SpitfireIX_5", 1, "spitfireix_nm_5", false}, -- {"SpitfireIX_5", ROUGHNESS_METALLIC, "spitfireix_5_dif_roughmet", false}, -- {"SpitfireIX_6", 0, "spitfireix_6_dif", false}, -- {"SpitfireIX_6", 1, "spitfireix_nm_6", false}, -- {"SpitfireIX_6", ROUGHNESS_METALLIC, "spitfireix_6_dif_roughmet", false}, {"SpitfireIX_4", 0, "spitfireix_4_dif", false}, -- {"SpitfireIX_4", ROUGHNESS_METALLIC, "spitfireix_4_dif_roughmet", false}, -- {"L39-LAMP_CPT2", 0, "spitfireix-cpt-cl", false}, -- {"SpitfireIX_1_SHTORKA", 0, "spitfireix-cpt-shtorka", false}, -- {"SpitfireIX_1_SHTORKA", ROUGHNESS_METALLIC, "spitfireix-cpt-shtorka_roughmet", false}, -- {"map_pilot", 0, "pilot_raf_kneeboard", false}, -- {"map_pilot", ROUGHNESS_METALLIC, "pilot_raf_kneeboard_roughmet", false}, -- {"Material #3108", 0, "pilot_raf_fp", false}, -- {"Material #3108", 1, "pilot_raf_fp_nm", false}, -- {"Material #3108", ROUGHNESS_METALLIC, "pilot_raf_fp_roughmet", false}, --[[bogus material: SpitfireIX_GLASS_PRIBORS]]-- {"pilot_RAF_FP_Notepad",0,"mfd3",true}; {"mirror_SpitfireIX", 0 ,"mirrors",true}; --mirrors texture replacement with runtime rendered one }To activate or inactivate the Naked350 Refurb cockpit mod I lift in or out my preprepared zip Cockpit_Spitfire_LFMkIX from: C:\Users\username\Saved Games\DCS\Liveries

I've learned (somewhat recently) that a flyby with hook down signals "I wanna land" on US carriers. Obviously accommodations for radio failures must exist. Doesn't help my Spit (neither will Russian livery I suspect).

Persisted for a long while (until I exited). Not seen on F10. Usually debris of crashed planes decorates runways. Maybe it's true the P-47 is really sturdy.

Took a shot of max lightning at night. Default placing, view angled down. Too dark IMO.

Seems really counter intuitive to put flagpole there. Can one / must one ask them to take it down before landing?

Similar / same as P-51 after last lightning fix (now 2.5.6.52196). Made a thread in P-51D forum. Read for more detail /context. Copying argument from that thread. I can't say it much simpler. Intuitively this is just too dark for daytime. Note sun position, above & behind. Three pics. 1) Panel at default distance. 2) Sun position for shot 3) Max light at night, also a little dark or ok? Note, images are noticeably darker in game (for me anyway).

Deleted everything in "OpenBeta\_downloads". Ie torrent files. Seems to be working (famous last words)... ~ Successfully updated.

Got a weird scary message about "32 unknown files" in "OpenBeta\_downloads". "which are not supposed to be there". "Make sure your custom download folder does NOT interfere with your working folder ... otherwise you may loose your files" Guessing this is debris from previous patches. But what are they even talking about? Can I delete all contents of "OpenBeta\_downloads"?

Just got a little reminder of this. From top, 1 of the 4 screws felt soft on re-tightening. "F' f* F' I threadened it". No it was spinning at the bottom screw. Never enjoying taking it apart. The anxiousness of screwing up. The original spring is so strong, it feels to me, it's threatening the integrity of the whole housing. Is it? I don't know, but I wish the four poles, the screws, all of it, would've been one dimension stronger. M7 instead of M6 or whatever. Another reason to weaken the spring, even if it has to be an expensive "green spring" from Sahaj.