wired521

Thanks @AeriaGloria - I let Petro set it but ended up waaayy of course (as in, probably 20 NM or more on a 60 NM leg). Moving map thought I was in the right area, but I wasn't. Maybe Petro is hitting the Vodka too hard; lord knows he's all over the place when you let him take the controls. There's the control in the Pilot-commander station that has the 3-way switch, anything to set there? I'll try what @molevitch provided (thanks for that).

Fighting thru a combination of the F10 map heading checks / petrovitch heading checks and lots of trial and error to get from point A to B. Just curious, why don't we have any documentation or content on the correct use of a critical (IMO) change like navigation? The one video I've found is simply 'how to set' the declination, but nowhere can I find where the values should be. It also seems like, at least on the Persian Gulf map, that the declination isn't static (and requires adjustment during flight). -42.4 seemed to get me in the ballpark, but after a 60NM flight it was way off (way off being about 20 degrees between indicated heading and what the F10 map or petrovitch show). Can we please get something (even a forum post) from you ED explaining how this should be used, along with reference values for each map?

ATM I'm just letting Petro do it; I was hoping they'd add declination info to the kneeboard. Otherwise, I'm not sure where to get it.

Hey everyone, I setup a mission with random failures and noticed that engine oil and hyd leakage failures do not produce any impact on the hornet. I made and attached a dedicated track file showing both of these failures triggered and yet no impact on the engine oil pressure (and it keeps running) or hyd pressure after ~1 hour flight time. I assume this is a bug considering these failures are listed in the ME, but if not please let me know! Also happy to provide any additional information you may need. FA18_RF_BUG_RPT.trk

Hey @uboats do you need me to file a bug report for this (with a track file)? Seems like others are seeing this behavior as well.

So current behavior appears to be incorrect, at least for me. Anyone else seeing this?

@WarbossPetross So I just did an entire sortie over FL20 (most of which was FL30 or above for endurance) without the oxygen valve open, no hypoxia effects at all. I don't think that it was coincidental that depressurizing caused this before. Perhaps something isn't working as intended atm? FWIW I've ran into this plenty in the F14 if I miss the oxygen switch on startup .

Hey guys quick question regarding oxygen configuration. My understanding is the JF-17 pit is pressurized; does the oxygen valve need to be opened at all times or only under certain circumstances? I normally leave it open and verify the blink light, but figured I'd test to see what would happen if I closed it altitude (FL32). I didn't have any issues after ~15minutes.... until I also unsealed the canopy . Then, I started noticing the blurred vision effect... although I'm not sure if this was related to the "icing on the cake" temperature modelling. Can anyone confirm if the oxygen valve is supposed to be open at all times? If so... any thoughts on why there wasn't a problem at altitude when I closed it (bug?)? I tried looking at the manual but it's still very basic... at lease the one that ships in the Docs folder. Thanks!

I'm experiencing this issue as well; conditions are: Type: 154A Mode TOO Release within Range Alt 30K feet MSN Heading 000 (also tried using HDG Undefined, same result) TGT altitude 15 ft (as set by mission editor) eFuz set to Instant Behavior is the JSOW will overfly the target, bank hard left and appear to establish a new attack angle. It never succeeds with this, and after the hard bank falls out of the sky. I'm wondering if the weapon thinks it's supposed to be ingressing from a different angle and it severely overcorrecting way too late. Anyone heard any updates on this problem?

Hey everyone, I tried the JF during the promotion... and bought almost right away :) Certainly has emerged as my favorite module in DCS - thanks to the developers! One thing I've been looking for is fuel planning resources for ground strike missions, and if possible estimated burn rates (under cruise conditions) I could use to calculate loiter times for CAS missions. Given the limited internal fuel capacity (although the burn rate seems quite efficient for the limited amount of fuel), deciding when to bring bags is important. Any general rules (or even better, performance charts) that others have been using?

Thanks Grunf - this took care of it. I think the issue was my RADAR was on previously. Just tried what you suggested and it worked. Thanks again!

I'll it another try - last time I did that the current waypoint switched from B(x) to E(x) when I pressed T1, then to b(x) when i pressed TV, then back to blinkin E(x) when I released TV. Isn't the current waypoint supposed to advance to the next after the fix? Also, by radar off is that A0 and master mode back in Nav? Thanks!

I don't have a 3-position switch on my flight stick, and haven't been able to figure out a way to do manual nav updates by flying over nav-type waypoints. I've tried several combinations of the 3 positions (individually mapped to different buttons) but haven't had any luck. What is the correct sequence for T0, T1,and TV for doing an update by overflying a visual reference?

Looks amazing!

Just wanted to share this tip in case anyone else wasn't a fan of the 'center position' the view snaps back to. After you set your view to something that works better for you, hit R-ALT Num 0 to save the camera position. Personally, I like a slightly tilted down view better. Just thought I'd share in case anyone else w/out track IR was curious about this.