Akula

Again, this is about CHOICE, not realism. You wanna treat this game like you're a real life fighter pilot, fill yer boots. It doesn't mean everyone else needs to be as hard core. More choice, more new pilots, more diversity in game and more money for ED.

A great feature that gives new players and players not used to combat sims the OPTION to auto refuel. Not arguing it’s realism. What I am arguing is the appeal of having the OPTION so that new players can fly with friends and in servers and on long missions without the fear and anxiety of losing an hour or more of their flying experience just because they ran out of gas trying to tank. Wanna attract MORE customers and make MORE money? Do this. Falcon 4.0 had it from the get go and wouldn’t you know it. I still learned how to AAR on my own even though I used that feature all the time while trying to learn it.

I’m using the MSI MPG Edge Wifi DDR5 and now have this voltage issue under control. For those who can cross interpret this info here are my settings. - Using the latest non beta released microcode. Profile set to MSI performance 253W. Wattage capped at 253 - Voltage capped at 1.33v That’s it. Load Lone Calibration and “Lite Load” are both on auto. Everything else is on Auto. core clocks are in the 5.6/5.7 range HWINFO64 reveals Core VIDs under 1.4 (that’s just the voltage the cores are ASKING FOR. It doesn’t mean they are getting it) Vcore voltage max is 1.238-1.3. Average Vcore hovers in the 1.1 range. Under load nothing exceeds 1.3 volts and temps don’t even reach 70c except for a brief spike when Windows starts up. DCS runs cool with temps well under 70c no stuttering and no lock ups or CTDs. PM me if you want to know more.

I’ve been tinkering with my 14900k since I built my rig in February and it’s a constant battle to get this thing under control. A few things that have really made a difference since the latest MSI Z790 BIOS. 1. run intel default settings and leave it like that. The frequency may say 3.20 base clock but even on Intel default settings the chip ramps up to 5.67Ghz under load. It actually runs great and very cool and stable using this one profile.No tinkering necessary. 2. I also disabled hyper threading and Ecores and it runs great. I haven’t yet tried DCS with HT and Ecores disabled but I did try it with just Intel default settings and it runs great and cool. Temps did not exceed 80c. I’ll let you know how it runs on #2. When I have a chance. Either way I’m still RMA-ing this chip as I’d rather gamble on a better batch the second time around. I just need to build up to courage to go through their PAINFUL experience as they do it on purpose to discourage their customers from making warranty claims.

I’m guessing this is because 40NM is the farthest range for any Fox3 missile’s highest POK (probability of kill). At angels 30 I usually launch at 35 miles and then notch as I dive, then go cold once the missile is at roughly 15 miles. By then the missile is on its terminal path and usually seeks out the enemy fairly easily. You don’t want to go too far beyond that as battery power is modeled into the fox3’s. This means that they can only track for a minute or so until the battery runs out and the missile goes stupid. I could be wrong about this so feel free to correct.

Many thanks @currenthill. Your contributions are what help make this game fun and enjoyably with this “out of the box” thinking for those who like having fun with DCS vs just flying it as a strict sim. Having CHOICE like this makes it better IMHO.

I agree with this. @currenthill It would be a shame to restrict it to content creators only since I’m sure many would like to try it in single player. I highly doubt these OP missiles would even be allowed on most servers regardless of wether or not it passes an integrity check. If you could please share it with the rest of us it would be greatly appreciated.

I know the F4 view will never render the internals of the cockpit like the F1 view. The F1 camera controls for inside the cockpit will give you the high res cockpit but it can’t do a floating camera view panning over the controls as shown in the video. I’ll keep digging but thanks for the replies If anyone knows how, please share.

Wondering the same thing. So stupid that creators will show it off and not share the fun.

I missed this part of your reply. I’ll check that out, thanks DZ

It’s not the system or the windows or GPU settings it’s the cockpit resolution and capturing it correctly. I have plenty of horse power to spare with my rig. Made sure of that. Try setting AP to level flight and then hit F4 and move the camera inside the cockpit. Don’t hit F1….. you’ll notice that inside the cockpit everything is very low definition and just looks crappy. I tried doing this in the air, on the ground, while flying as client, player and even tried moving the camera into an AI’s cockpit. The cockpits all look low definition.

June 2024….. I’m having this issue as well. I have not tried the training although I completed it years ago. I just went back to see if I could do it and although the timer showed up once on the MAV MFD it never showed up again and MAV is still crossed out. I selected my target with the FLIR, locked it up, all good. TDC switched to MAV MFD and uncaged it. at this point the MAV display shows it uncaged, timer on HUD says within range. Set to AG, Master arm has been on since before ingress and STILL - STILL MAV is crossed out.

Can someone PLEASE help with this. Check out the chinook video. I’m trying to capture HIGH DEFINITION cockpit videos such as what you would see at 0:10 every time I try to capture in game video of the cockpit instruments the entire cockpit looks like it’s rendered in 480p which is nowhere near what you see in the chinook video at 0:10

EDIT: This is in the Hornet. June 2024….. I’m having this issue as well. I have not tried the training although I completed it years ago. I just went back to see if I could do it and although the timer showed up once on the MAV MFD it never showed up again and MAV is still crossed out. I selected my target with the FLIR, locked it up, all good. TDC switched to MAV MFD and uncaged it. at this point the MAV display shows it uncaged, timer on HUD says within range. Set to AG, Master arm has been on since before ingress and STILL - STILL MAV is crossed out. I tried resetting everything. And I could not get the timer on the MAV MFD to appear so I’m guessing these things aren’t warming up…..? I don’t know. I must be missing something but I just can’t figure out what it is. I’ll do the training and see what the F it is that I missed but if anyone wants to take a stab at this and tell me what I missed, that would help. The pigs never gave me this issue lol. TIA if anyone wants the track file let me know.

Thanks... Makes more sense now. I wonder why RAZBAM did this. We can assume it was malicious, which I doubt; but we can also assume this as a safeguard to prevent ED from taking their intellectual property and continuing on without RAZBAM if they abandon the module. If that's the reason (AGAIN no one knows for sure) then is it logical to suggest that ED may not be the good faith actor we think it is? Fair question to ask.

A timeout on a feature does seem sketchy. I’ve never heard of something like this before nor have I ever heard of a reason to code such a thing to a module. Anyways, keep calm carry on and fly something else while they figure this thing out in the courts/hearings. excuse the caps but: “LET’S NOT MAKE THINGS WORSE BY GUESSING.” Gene Kranz Flight Director - Apollo 13

Why not? Just curious. Seems so strange that such a jet can’t be fitted with hard points that accept external tanks.

@BitMaster Most users HATE GHUB as it seems to completely disregard older Logitech devices. This is not new and Logitech has been aware of this since GHUB was released. They still haven't fixed it in GHUB. Stick with the latest version of Logitech Gaming Software as it seems to be the most user friendly app for all Logitech devices vs just the newer ones.

UPDATE: SOLVED HOLY - F! - I never thought I'd be able to fix this on a Windows 11 machine. Here is what I did. Keep in mind this is in 2024 as all other fixes are VERY outdated. Stick with Logitech gaming Software (V 9.04.49) Locate Lcore.exe (usually found in C:\Program Files\Logitech Gaming Software) Right click Lcore.exe and click "properties" Click the "Compatibility" tab Make sure "run as Administrator is checked Click "Change High DPI Settings" Make sure there is a check in "Override high DPI scaling behavior" Under that, choose "Application" and OK your way back to Desktop Reboot PC Once PC is fully booted and running open up the Logitech Gaming Software Choose your mouse and in the Home screen for the mouse make sure you select "On-Board Memory" and click on the GEAR ICON WITH THE ARROW Play around with either the "Assign Default" or "Assign Shift" to "jumpstart" your DPI into working again WITH the lights. DONE! you can now customize and set your DPI settings and they WILL work. This is how I was able to fix it on a Windows 11 machine so give it a shot and please let us all know how you did so we can help others Cheers

A bit of a rant but my research has not been able to find a solution. This is soooo F-ing frustrating to say the LEAST! I happily own (and with NO INTENTION to throw out perfectly good products) the following from Logitech: Logitech G19S Keyboard Logitech G502HERO Mouse Logitech G922 Artemis Headset THEY ALL WORK PEFECTLY. - What doesn't. BOTH Logitech gaming Software (V 9.04.49) AND Logitech Ghub (latest version as of May 11, 2024) I really hope someone can help because it seems the entire internet has moved on from this chronic issue which remains unresolved to this day for many other users. Here's the issue many are still suffering from. - Install Logitech gaming Software (V 9.04.49) and it detects ALL devices BUT!!! - the DPI on the mouse just will not work and YES, I tried setting it to onboard memory. It STILL will not work. the lights work, greeeaaaaat. - Install Logitech Ghub (latest version as of May 11, 2024) and it detects and runs perfectly the mouse and headset BUT! - Will not detect the Logitech G19S Keyboard. So I'm left having to choose between one or the other depending on what features I can and can't live without. Can someone PLEASE help! My stuff works but is being actively "undetected" on purpose, is the feeling I'm getting just to force me to upgrade. I uninstalled GHUB (useless) and sticking with Logitech gaming Software (V 9.04.49) for now until I can figure this out. TIA

NO!, This is not our problem! Whatever financial woes ED has now is for THEM to resolve using the funds WE HAVE ALREADY GIVEN THEM. - And imagine if they adopted your scare tactic of "Pay us monthly or we close up shop and now you're left with Falcon BMS." Thank god you don't run the company.

Can we please stop putting stupid Ideas in the heads of ED’s CEO’s?….. they’re already trying to get out of the financial mess they put themselves in. WE PAID THEM! THIS IS NOT OUR PROBLEM

In one word - NOPE.

This discussion is about automated AAR and like I said. The bottom line here is that all players should have the choice. Nice try to cop out of a constructive rebuttal.

Set page file to 16384. Same crash before take-off and happened right after I "unpaused" Trackir. Log file attached. dcs.log