PawlaczGMD

Please assist in crash diagnosis. dcs_1lcrassh.log

Looks like I had a: -faulty stick -didn't set up telemetry and profiles correctly. I replaced it now, and my original complaints are mostly gone. I will do more testing of pulling high G at high speed, but trim works correctly now. Would you mind sharing your Moza profile?

My new stick just died ;_; I had all that set correctly. I think with Moza the telemetry FFB might work better. I got to try their Hornet profile before the tragedy, and it felt completely different than Direct. I will test it again after replacing this junk.

I just got the Moza FFB base, and tried the Tiger in Direct mode. AFAIK, this is supposed to use the in-game implementation of FFB. Is this the "best" setting I could be using for this aircraft? I've noticed some issues, such as: -The trim for level flight seems to be different than non-FFB. I need to trim all the way down and then push the stick more for level flight at high speed (600 kts) -The physical stick doesn't move with trim, the in-game one does -I did not notice any noticeable stick force increase at high speed and ripped my wings, which I have not done in a long time with non-FFB. Are the "bobweights" implemented? I'm looking for suggestions more than complaining.

The problem is that the AI is doing all turns at max performance. It's practically impossible to follow their turns in formation, unless it's a minor course change.

I still have trauma from when they outclimbed and outturned me in a Tomcat.

I find that some people often complain unjustly about AI flight models, but the Mig-21 really has a lot of excess performance. It is nothing like fighting against a player.

Same, I got engine degraded after cruising below max continuous settings on RTB after a long mission. Temps were normal, then suddenly Engine degraded, than a minute later oil temp spikes and the engine seizes. Water injection was used in combat 15-20 minutes prior to the failure.

This guy Contact light has compiled EM diagrams for many jets, albeit in the clean config. Take a look: https://cdn.discordapp.com/attachments/1092582325591740516/1092610587843903528/Subsonic_Energy_Maneuverability_Diagrams_for_DCS_202304.pdf?ex=67a6a8e7&is=67a55767&hm=9dbf6f3d5f797cc712596198ffdc30b97ce98e3c29aadcb678495d81f184d4ea& Max inst rate seems to be an 8g pull at around 300 kts.

Thanks, my method was generally correct, but that's a lot of good info. I managed to do my mission by boresighting in the air at around 8 nm, which didn't give me a perfect handoff, but was good enough. I'm used to the Hornet where it just works. Is it just that the Hornet doesn't have this effect modelled? Or is it just smart enough to do it by itself?

Thanks for the tips. Looks like I was doing everything correctly, except I should try to boresight a target that's closer to the intended real target range, so maybe 8nm. I was using closer objects for practical reasons - it's hard to resolve a specific building or object that's not IR hot at longer ranges. Doing it on the ground would be best, but in this mission there are no good targets to lock up near the airbase.

Master arm to ARM, GJ off. Do I need GJ on? Maybe that's the missing step. But I am doing the boresighting in the air, not on the ground.

Can someone give me tips on how to boresight the mavs from a cold start? I do it in the air by locking some building on the way in the tgp, aligning the maverick, locking, and pressing BSGT. The target was a few nm away and the BSGT button lights up. However, when I then try to engage real targets around 8-10 nm away, the Mav points at least 50-100m away from the target vehicle. Auto handoff will never work like this. Am I missing something, or is it just what it is? This makes engaging clusters of targets very frustrating. I spend a few nm of travel just fiddling with the maverick manually.

That's just not true, the Corsair and La-7 full fidelity official modules are in development by 3rd parties.

The Viper INS+GPS has modelled errors, in practice you cannot drop blind on steerpoints even with JDAMs, as they work in relative coordinates mode. You always need a sensor track to be precise - until they change something.

My point is exactly that it's a poor financial decision by ED. A player reeled in by being gifted a $10 FC jet might spend hundreds on full fidelity modules. A player not excited by the Su-25 will drop the game.

Something like this is actually a good idea. The average player interested in a combat flight sim is probably expecting to do some air to air in a fast jet. What is offered for free is a slow Russian ground attack plane and an unarmed prop. DCS as a "free" game does not present its content very well. Yes you can do a trial, but I bet someone not already playing doesn't know that, and is not willing to figure out how to do it, they just want to play the "free" game to see if they like it.

Yes, I am very happy with the AMD raw performance / price, and would recommend it if you don't upscale. Sadly, it has a couple of lacking niche features that I want: CUDA and running AI on Windows in an easy way.

Yeah, I already have a 7900 XTX, so the only 2 things I was interested in are: -DLSS4 (FSR sucks in DCS) -CUDA Maybe FSR 4 will be much better and usable, I will wait and see. I can always get a used mid range Nvidia card to run my CUDA stuff and just run 2 GPUs.

Yeah, I saw that. I might hold off on both Pimax and GPU upgrade until next gen.

The options.lua file just seems to contain all the settings in the in-game options menu. Can you tell me which line is relevant to Vrem? I don't really want to overwrite all my options. Here is my current file. options.lua

thanks for your work, but the dehaze still doesn't work for me in VR. Reshade 6.3.3 with addon and Vrem 7 are installed.

FYI, I've found this chart of what new features are available on which gen.

Are you saying DLSS 4 works with older GPU generations? That would be interesting.

You're right, I just checked, and this weapon has both airburst delay and altitude in a single fuze. I have no idea how it works from the loadout menu information.