Akula

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

@BIGNEWY Starting to wonder if this has anything to do with Tacview.... The CTD occurs just before, at or shortly after take-off. Is there anything I should look for in the Crash log. What are the triggers you usually look for when going through the logs.

Update, No change to DCS since last crash log. Still crashing. FYI, all drivers, BIOS and updates installed. Everything is up to date and I am not having this issue with other games. Updated to latest patch. Ran a test flight, - CTD Removed F-22 MOD. Re-boot Windows 11. Ran a test flight, - CTD Ran a repair successfully. Ran a test flight, - CTD Latest crash log attached. dcs.log

Thanks Newy, but I have a feeling this is more patch related vs MOD related. I'll try with the update first and see i it helps. If not I'll try with the F-22 mod removed and report back. For the record, the update states it is addressing VR headset related CTD's. I do NOT own or use a VR headset with DCS or any game on my PC. - Let's see what happens

Getting a CTD when in DCS. This happens either at or near a mission start. Log file attached. dcs.log

He's just proving you right with every comment. Anyhoo, don’t mean to skew this discussion. Carry on lads

@LOW_Hitman The changes you make are reversible and won’t brick your rig. You do what you want. Your back handed comment is unnecessary and and misguided. Try to help people and this is the <profanity> they spit at you.

If I were you I'd try some of the tips AFTER some research and quite honestly, it doesn't take much research to find out if a change or "tweak" in Windows such as disabling the scary "power" thingy in Windows will brick your rig. If it doesn't work you can always revert back. I've been using and building my own rigs since 1995 and I have probably run into a Windows setting that royally F-ed up Windows to the point where I had to reinstall the OS in it's entirety, ONCE. Since 1995 it has happened ONCE. I'm 52 so yeh maybe it happened twice as my memory is so fuzzy in this context due to this hardly happening. If it scares you and you don't wanna do it then don't but you need to understand that the days of Windows completely dying on you because of ONE change to a setting the DEVS created as part of the OS are long gone.

Best advice I would give is to fly the jet. As long as you're on the ball-stable, your hook is down and you are aiming for the crotch of the ship at 3/4 mile you should be able to fly it in without too many adjustments. Try straight in landings first and get used to them. Once you are comfortable with that do case 1. Let your head and muscle memory absorb the visual cues on final until you can do it with your eyes closed. Case 1 is tough to get right as per the text book but it's not impossible and takes time to perfect. Lastly, fly the jet.