-0303-

Remade top post. New video in higher game resolution (1920x1080) & zoomed in. New screenshot in exact same position daylight. Changed all text (discovered new things with better quality). Specifically, the G-meter (top panel) red/yellow does not wash nearly as badly (still red/yellow) as IAS red/yellow needle (completely white). 1) Shouldn't all colors act like the G-meter colors? 2) Is the gauge color washouts just me? Feedback, players? Made preparations, gathered files for bug report, don't want to waste DCS time if it's just me. (Youtube is crappy, might upload an mp4 when/if making bug report)

I couldn't find any in the right size so I tried to make my own from piano wire.

I'm soo tired of disassembling & reassembling the Warthog stick:cry: (to weaken spring force). Heard of all you reference, tried most. Tried making my own springs ... less said the better. Always afraid of breaking something. Important lesson learned: On reassembly, the rear plate must be removed (& pcb lifted), to tighten the four poles from below as well from top. The four poles cannot wiggle, it'll make the stick wiggle and worse, it probably wears down the screws and threads with time. Anyway I finally tried tried springs-on-top (see your video below). Been skeptical because 1) it'll probably be to loose, 2) it isn't meant to work this way 3) springs are never meant to be fully compressed and maybe this way they are (might or might not be a concern with these springs). Anyway I finally tried springs-on-top. I found: 1) One cannot add even one washer without loosing stroke (this means springs are definitely fully compressed). 2) It is too loose. a) Resistance is needed. As mentioned mind remembers force better than position. b) Not having return to fixed position, trims are unusable. c) The strong spring protects the joystick from damage reaching full strokes. With as weak resistance as this, it's a matter of time before I'll slam into a stop and break something. Maybe I'll try binding the spring again (photo below). I did it differently and it didn't work so great. Even small zipties are to big. Sewing thread applied while temporary held with zipties ... didn't work so great. Haven't tried metal wire. Maybe I'll have to spring (get it?) for Sahaj expensive green spring:mad:. Warthog stock definitely does not work well with helicopters. For the record. TM Warthog is good except for the stick gimbal, throttle is good, the stick is robust. Flaws are unadjustable spring forces, X & Y axis not separated. And also it's a pain to take apart. Especially taking apart the gimbal fully to clean and re-grease is extremely tricky without breaking something. But apart from that, good reliable stick.

Tested opening COMM menu Spitfire & P-51. Note, radio on or off doesn't matter for opening COMM menu. But the menu do other things then radio, so that makes sense. EasyComm off. Offline mission (homemade, just spawn Batumi). Ground: Both PTT and "/" works. Air: PTT works and "/" doesn't. Online. Hoggit training server. Ground: Both PTT and "/" works. Air: PTT works and "/" doesn't. Aerobatics Server. Ground: "/" works, PTT doesn't Air: "/" works, PTT doesn't. Guessing EasyComm is set this server.

Argument by analogy. If you stand in the middle of a room with windows daytime, you will be able to see the texture of the wallpaper. Sitting in a cockpit, daytime, less than a meter from the instrumental panel, light coming in from a 180 degree arc from above (the canopy) ... Even inside cloud one should have no problem seeing the panel textures (*1). Deliberately not a bug thread since these are random screenshots from yesterday and it lacks a specific comparison (to old patch). Proper way to do it might be to spin around on the runway (to get all angles). Downgrade patch and then use same track to spin around again. Apart from assuring a "clean" client and supplying logfiles and track. Make a splitscreen youtube video. I don't feel like taking that effort. Asking for opinions. Is it too dark? I'm running an absolute minimum settings. Could this be an artifact of that (even though I see a difference to old patch)? ~~ *1) I know this for a fact. Not a P-51 but in a Bergfalke-III. Disobeyed rules, just a little, crept up a little inside a cloud and encountered snow!. A really great day. No problem whatsoever seeing the panel texture.

After In any daylight situation one can see the texture of ... things, instrument panels in this case. Now one can only see texture when the sun is angled directly at the instrument panel. Also, night situation, the cockpit lights illumination is now weak, too weak. I liked the warm yellowish light pre 2.5.6.50726 provided by cockpit lights (even in daylight). I recognize it might have been too light, but this is too far in the other direction. I noted someone complained about the same in one of the german planes a week ago. ~~ Sun directly on. How you should be able top see the texture in every daylight situation. Even inside a cloud (obviously "greyer"). Below. Every other angle (sun in face or not make no difference, included sun just for artistic reasons).

My Saved Games was corrupted. No snap views saved for any plane.

I used to follow the data plaque right side (cruise +7lb Boost @2650 RPM). It's says 9 lb for climb. I notice now that manual states 12lb 1h and doesn't say 9 lb anywhere.

No bug (for BigNewy, Nineline). I saw something similar. I decided I imagined it and dismissed it. Did a test: Film. Spawn RWY Batumi. 50 knot (25 m/s) headwind 130', 20'C. Radiators fully open. MP 25 (no overheating). Accelerated time 50x. Video 50x for total 2500x. Looks normal continuous consumption. So I did imagine it.

It isn't supposed to burn ... Rear tank, drop tanks works fine. Just tested. Have worked since december 2019?

Did you read what I wrote? i saw two instances, including myself, where visible damage was not consistent with actual damage for the client in question. Meaning communication of damage to other players might be bugged or glitchy.

Besides throttle one can switch radiator Off (fully open) [A] toggle. I'll do that when oil temp exceeds 80. Don't exceed 85 says manual. Unfortunately to keep oil pressure below 120 I found one needs to keep oil temp near 80 at full throttle. Really whenever one applies any throttle oil pressure gets close to 120 it seems. Oil pressure should be between 60-120. I could have sworn oil temp was supposed to be 60-80 but reading manual now it says 20-80. Specifically manual says: and I can't find "60" anywhere referring to oil temp.

Same. Also. Snapview saving doesn't seem to stick. Have to redo every session.

Is there subforum here (not github) for bug discussions? I think more people would discuss them here. Dedicate a bug forum to it here. This could weed out known issues before posting to the Github place. I believe there's panel lighting bugs reminiscent of all the lightning bugs affecting a lot of DCS planes (Spitfire, Su-33 ...) also affects A-4E. The wheels warning light and the AoA lamps definitely display the same color error as the Spitfire LG lamps. Differential wheel braking doesn't work. Braking one brakes both. It explodes to easily on the carrier. Controls Indicators doesn't work.

Install says: Should say

Isn't there some kind of "frequent flier miles" for full prize buying?

Seen "the original gif"? It's smaller.

I recognize the flaws but there's nothing else like DCS on the market. Fullest most accurate simulation available. So, yes, satisfied, if yes / no is required.

Confirmed. Start / stop animation non existent.

The corrected Figure 5.8 page 178 (see previous post #128). Been ready for a year but I lost interest ... Made a new page 178 (complete with drop shadows) and replaced page 178 in the DCS PDF manual. But I'm not allowed to upload a new PDF I think and even if I were, there are multiple more pages that are also wrong, it's to much. Anyway, here's a max resolution 8126x10632 bitmap (well, it would be, except imgur compressed & reduced size (7MB -> 2MB) on upload) of my corrected Fig 5.8 page 178 PDF. I really enjoyed digging into the F-86F blueprints and made every effort making sure this is correct for our version F-86F-35. Note, names are all copied from the original manual, skipping the made up names in the DCS manual. I wanted to be more ambitious and improve the text blurb which is unclear (before losing interest). I'll say something about that now. DCS manual says, page 179: This doesn't make clear that the stick forces are completely 100% artificial with zero zilch aerodynamic force stick feedback. The F-86F stick resembles more than anything else a spring loaded joystick working exactly as our desktop joysticks. One difference, the F-86F trim moves the spring loaded center position of the "joystick". The sticks position directly control hydraulic actuators, which, again, are completely disconnected from the stick. Rudders are conventionally connected with wires (so from the rudder one would feel aerodynamic forces). ~ The original manuals are really good, read them before the DCS manuals. Find here. They would be, one would expect, written for real, not for a game, and also, counting 1949-1994 service, 45 years of pilot correcting feedbacks (there's forms for that in the manuals).

Opinions before making an "official" bug report. Does gauge colors wash out at night this much for everyone? 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 all gauge colors should look? First daylight colors for comparison with night. 1920x1080 (min settings). Bad youtube quality [43 sec] (adjust best youtube quality, go fullscreen): 1:00 AM, spool up max Cycle "Instrument Panel Primary Light Rheostat" min - max twice Interestingly, this behavior changed with latest patches (most likely Open beta 2.5.6.50726 with it's list of "Corrected lights in the cockpits of next aircraft ..."). Better in one aspect. Used to be, turning up full "Instrument Panel Primary Light Rheostat" even in daytime, gauge colors washed out completely.

Good idle, fine!:). But autoscript 1300 rpm does redline oil pressure which is not a good look. So 900 rpm warmup until 1300 rpm can be applied without redlining (a minute maybe). Overall, the manual makes perfect sense to me. Cold thick oil = no lubrication (which can be mitigated with gasoline oil dilution). Nurse warmup with/without oil dilution (autoscript does oil dilute), the important thing is to never redline oil pressure.

The DCS P-51D manual says 40'C oil (and 60'C minimum coolant). But forget the DCS manual and read the real manual (April1944). It does say 15'C (see 2nd pic) but in warmup it emphasizes gauging oil pressure with throttle opening. Did an experiment. Watched oil pressure and temps. Found that: 1) To be able to apply full throttle without oil pressure redlining, you must wait until 70'C oil temp (start of green arc). 2) But with oil diluting (note, max 2 minutes) one can apply full throttle at lower temps (55-60'C, don't quote me). Note the Emergency Takeoff note. Oil pressure is what really matters it seems. And you gauge that by applying throttle and watching the oil pressure. A max throttle takeoff requires 70'C oil temp to avoid exceeding oil pressure. But, in a hurry, one can oil dilute to keep oil pressure down and still max out throttle at lower than 70'C. A third option is applying less than max MP (MP 30 is good enough for takeoff), this will keep oil pressure below redline at lower than 70'C. To be real finicky about it ... the autostart script goes to 1300 rpm and exceeds oil pressure max, not good. Read elsewhere that 900 rpm is good for warmup (the guy who ), high enough to not foul spark plugs. So ... manual start, use 900 rpm warmup for max nerd factor.

Yea, still would like to do this. The ability to scale images in the forum. On another board this can be done. If for example there's a gigantic image 10000x10000 or whatever I can just specify 800x800 along with the image's URL. Instead of having to painfully resize images in GIMP/PhotoSHOP/PAINT until they seem right.

Joined 2018. Always been this (annoying) way.