Loukuins
-
Posts
476 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Loukuins
-
-
3 hours ago, jackill said:
I have basically the same CPU, but from, the beginning I am using mt.lua added to Saved Games\DCS\Config and for fps limiter just Radeon Chill.
multithreading = { exclusiveMainRenderCore = false }
Maybe you could try it.
The screenshot was taken with the lua file. I've been using it since it was released on the forums
-
I stopped playing for 8 month, come back, and the issue is STILL HERE, 4 threads at 100% usage, lost 100fps, now running at 60fps, instead of before V-sync locked 175fps.
-
1
-
-
29 minutes ago, Mini_is_Drunk said:
Well ED is developing the F35A with mostly speculations, public info and Pilot data, why cant Aegres do the same.
Because you can't do that, unless you add some imagination to it, ED assumed it and explained it when they announced the aircraft. You just can't do a good simulation of the aircraft if you uses videos and stuff like that, the amount of calculator and the little details of the different system make it impossible.
Especially all the calculations of the systems that needs to be accurate to represent the perks and inaccuracy of the aircraft it self.
-
On 5/1/2025 at 3:18 PM, jojo said:
I don't know if you're speaking only about export airframes or also French Mirage F1.
For most of its career, Mirage F1 CT got SHERLOC, then it both CR & CT got AIGLE.
But from the little I saw, Mirage F1 CR & CT AIGLE display looks to be close to Super Etendard Modernisé SHERLOC display which was better than Mirage F1 CT display
AFAIK AIGLE and SHERLOC (From the SEM) are similar or the same, but there is not much info on it, so I can't say, I was also speaking for non upgraded airframe
-
19 hours ago, Sarge55 said:
But it is important, otherwise why is it there?
In specific conditionsm mostly when you land with a lot of weight
-
1
-
-
On 4/17/2025 at 11:12 AM, Hiob said:
With the F1 it is really important to use the chute and only touch the brakes when already slowed down a lot. At least that helped me to finally get reasonable straight landings.
Generally though, as others already said, the ground handling physics in DCS for the most part is a big weak point. Some Aircraft like the F-14 do reasonably well, but most of the times most other aircraft (including Choppers with Skids) have weird friction/stiction values that simply don't feel right. And the directional stability of undercarriages on landing is....
well, "challenging" to put it mildly.
Chute is not mendatory in the F1
-
23 hours ago, Bremspropeller said:
I do have similar issues with the F1, but the most important issue is the inability to just floor the brakes without the airplane going for a ride.
I can nail the pedals to the floor in any other DCS aircraft and it will go straight ahead (no wind, etc). The F1 will buck like a Bronco and give me a heart attack, while starting to go sideways in an instant. And that is even without going all in on the brakes.
This has been a known issue for years now
-
2
-
-
7 hours ago, Ad0X said:
Yep, so even if we got a fully featured F1E with hud and ground telemetry, I'd be fine with the BF reciever, as modelling another rwr would take up too much resources. After releasing the F1M, the ground radar modes will be done, so a theoretical F1E would just need to have that HUD and radar modes implemented into the EE (ofc some coding required, but not as much)
It's a completely different HUD between the F1M hud and the VE120C HUD that the E variant uses (except the EE)
-
12 hours ago, Ad0X said:
Yeah that would make sense. Afterall, french didnt operate any E models, which were the main focus of my comment. I would just love to see a fully embraced "export" F1E with all the bells and whistles it could have. Hud, CCIP, ARMAT, INS. Even if it wouldn't feature a digital RWR as that was apparently a late 80s thing.
Only the EQ-6 got the SHERLOCK RWR but I have zero info on how it looks, the AIGLE RWR there is a few info on the internet on it
-
1
-
-
34 minutes ago, Ad0X said:
ARMAT definitely flew on Mirage F1s. Over 60 were delivered to Iraq and used succesfully in combat. Along with the delivery of jamming pods and RWR/internal ECM equipement, Iraq and France formed up a program to procure anti-radioation missiles. Current Anti-radiation missile in service was the MARTEL, which was jointly produced by UK and France. UK didn´t want to sell it to Iraq, so the french company MATRA developed replacements for the british parts in the missile and also developed a new and improved seeker called "Adar". The new missile was called ARMAT (AntiRadiationMATra) and was able to be fired from a F1. The iraqi "Baz´ar missile" was just an armat produced with Iraqi electronics.
The launch sequence was as follows:
Warm-up the missile at least 3-5minutes before launch.
Once warmed-up, turn on the seeker and start listening to tone.
Once a radar was dected, tone was heard and a guage in the cockpit indicated what radar frequencies were detected. If they matched to the radar that was meant to be destoyed, the pilot manuevered the launch aircraft into the launch envelope and launched the missile.
The missile was fully F&F.
The radar´s possition and frequency had to be known in advance and pilot had to fly into the engagement range using his INS.
The missile was quite sensitive, even so that radar hundreds of kilometers behind the targeted radar could be picked up by the missile´s seeker and mistaken for the closer radar. Because fo this, the flight plan had to be well-prepared to account for this.
Other than that, the launch aircraft didnt need to have any provisions or alterations made to it. I wasn´t able to find any pictures of the cockpit gauge and I dond ´t know where it was placed in the cockpit.. The ARMAT was launched by both french F1s in testing and Iraqi F1EQ-2s and onward.
As with CCIP/CCRP, the E model was from the get go meant as a multirole version and the Cyrano IVM radar had the option to provide A2G telemetry, spain just choose to not include the software afaik. The Iraqis practiced with CCIP/CCRP.
The source below is a 3 part recollection from a test pilot and other members who took part in the French-Iraq cooperation. It mentions the whole ARMAT situation and its the use in combat. The 3rd part mentiones CCIP and CCRP (called CCPL and CCPI in the source)
https://henridewaubertdegenlis.wordpress.com/tag/les-programmes-secrets-avec-lirak/
I was mostly talking about French Mirages, only the CR had the capabilities but there is only pics with the prototype, I'm not surprised that Iraqi could use them but there is almost no info on that except pilot experience.
-
21 hours ago, ChrisG73 said:
Well….my sincerest apologies for even asking, it wont happen again.
Sorry if it felt aggressive it wasn't and they just take the time it needs to work and make those stuff right, also they are working on making the Mirage F1 code more usable and future proof it to use it on the F-104 and F1M.
Also you can of course ask for it, it's fine
-
2
-
-
3 hours ago, ChrisG73 said:
I’d love to see some screenshots…..any sneak previews available?
Devs said they will show it when they will feel confident to show it, and I quote "In summary, it will be ready when it's ready and shown when we deem it worth to show but good progress is being made"
-
1
-
-
21 minutes ago, Chapa said:
Thank you for the suggestion but I’ll wait that ED provides DLAA official J/K support for that.
I don’t doubt it could improve but there is clearly an issue with F1 textures.
There are of course some aliasing and shimerring with my current settings because I don’t use any AA at all, only PD increase. The F16 and most of the planes are great (satisfaying for me at least) but the F1 is a dance floor in a night club
Nvidia has OFFICIAL support for that through your drivers, you might need to wait 3 months for ED to update on DCS and I don't believe they will add a feature to change the model.
-
On 2/16/2025 at 2:39 PM, Chapa said:
Hi,
I don’t know if already reported but the textures are very flickering in the F1 in VR at least (Quest 3, PD1.3). Black textures are always the worst but for the F1, the effect is really really strong and mainly due to the bump effect in the texture.
It is not a headset setting to adjust, I know very my headseat and all the settings I can tune with it and in DCS. (Using DLAA will of course remove it with the clarity in the same time, cockpit shadows also improve the situation.)
I don’t have this issue with other planes.
It is a great module but this issue breaks the immersion a lot.
Could be great to have a fix or an alternative texture that could be selected in the plane settings.
Thank you and have a great sky
Please try the J or K preset on DLAA, you can have easy tutorials to use it
-
On 2/13/2025 at 8:26 PM, Rudel_chw said:
I have that same skin and it works fine:
So, I doubt that the skin itself is at fault, more likely you have installed a user texture Mod that is conflicting with the skin.
This skin was not updated and right now has isssues look at the engine air intake
-
On 1/28/2025 at 3:38 AM, Cgjunk2 said:
I'm struggling to enjoy the F1 due to the sparkles as well. I understand that the physical texture of the real cockpit has a bit of a "spray on bed-liner" look, but it's almost as if the bumpy textures of the cockpit are literally modeled as tens of thousands of tiny individual bumps in 3 dimensions. It seems a bit too much in terms of granularity of details, no pun intended.
Maybe they can make a VR friendly cockpit texture for all of the offending surfaces? I'm running pretty high resoulution on my quest3 (at the expense of frame rates) but this is the only cockpit with such distracting shimmers. And it's been exactly the same since day 1 of release.
Was MSAA broken when this module released? I used to use DLSS and just tolerated the ghosting, but after trying to fix stutters, I noticed MSAA was better all around. I went back to DLSS recently and it seems just as broken in a different way....everything is immensely fuzzy compared to what I remember. In any case, I don't remember DLSS fixing anything when I was using it. It was still pretty bad shimmer.
It's because ED updated the DLSS model without properly doing it, aka they did it the easy way and not properly checked each model of the dlss dll.
You can fix this by using the new nvidiaprofiler and update your NGX folder to have the new Transformer model J or K, and try with them. -
23 minutes ago, felixx75 said:
After a long time away from F1, I've started flying F1 again. But somehow the flightpath marker is not displayed in aproach mode. Has something changed or is this a bug?
Check if you have no weapons selected, and that the master arm is on the off position
-
1
-
1
-
-
1 minute ago, MAXsenna said:
Cool! Did you watch OP's track, and understand what he's on about?
I think he is not letting the ADI and the Backup adi to align which takes time, or he thinks that the F1 has a HUD just like the 2000C for exemple that's all I can understand, because he said
"But it doesn't matter how I align it because it turns out the same every time. Thank you in advance."
-
52 minutes ago, MAXsenna said:
Did anyone actually bother to watch OP's track and understood the problem? I'm away so I couldn't myself.
Of course les Français would call a "HUD" something else. Affichage tête haute Sight sounds better.
Sent from my SM-A536B using Tapatalk
In france ATH (Affichage Tête Haute) is litteraly the translation of HUD
-
43 minutes ago, Snappy said:
You still didn’t really get the main point, did you now?
Well nevermind, you‘re way too busy being self-opinionated anyway.
Bro, stop being trigged because you were wrong one time, it's fine everyone make mistakes me included.
-
On 1/17/2025 at 9:35 PM, Joebejammin said:
But it shows a lot more than vertical speed? I mean the main point is you're being very disingenuous when someone references the HUD on the F1 and you're like "what HUD? The F1 doesn't have one, I have no idea what you're talking about". Because obviously anyone can deduce what component of the aircraft someone is talking about when they're referring to the HUD in an aircraft that has a "sight" that includes a ton of traditional HUD info.
But even beyond that, the HUD in the F1 includes and is not limited to:
- Altitude
- Heading
- Pitch ladder
- Bank indicator
- Radar range
- Time till missile impact
- Computer calculated target interception angle
- Gunsight and radar assisted pipper
The point of a HUD is a display that lets you have your head "up" instead of "down", and all of this information on the sight was previously relegated to the instrument panel, therefore introducing an improvement on letting your fly with your head "up". Just because the means of projecting the image is optical instead of digital doesn't change the entire function of the display.
I'm sorry but even the maker of the aircraft and the maker of the Sight is calling it a SIGHT. You can contact Dassault if you want them to fix that. And that you know better than them.
And yes it's different.
-
On 1/16/2025 at 12:11 PM, Snappy said:
Loukins this is not helpful. Yes , the manual may still call it a "sight", but for all intents and purposes the Mirage F1 CE,BE,EE already have a HUD.
I mean, seriously, what more would you need to make it a "HUD"? It has a flight path vector, its has a target designator box during radar lock,it even has steering cues to the target, it has a pitch ladder, it has an aircraft symbol.
It is definitely not a simple optical sight , like those found in the 50s vintage aircraft, as F-86, Mig-15, or even F-4 for that matter.
Technically it is a HUD. In the end, a HUD is also an optical sight in the purest sense of the word.
Bro, it's not a HUD, it doesn't have a FPAS, it just shows your Vertical speed in the sight, also it's a sight because all the stuff you see are mechanical and cannot be changed. Mirage F1CE, BE, EE don't have a HUD.
To have a HUD it would need a somewhat of a Navigation system (yes the EE does have one, but it's pretty barebone and is very close to the Super Etendard one.) and a proper HUD with digital input/output to properly customise and have all the info of a HUD. (Also HUD means, Heads up DISPLAY and there is no display in those version except the cathodic monitor of the radar)
Yes it's not one from the 40s-50s in what you can see in early Cold War aircrafts, but one of the latest Sight with good engineering behind.
A HUD is not a optical sight because it uses a DISPLAY to show informations.
There is no calculated FPAS or anything, it's a sight with mechanical sight you can move. The sight is linked to your GM switch.
-
1
-
-
On 12/12/2024 at 8:30 PM, 303_Kermit said:
Halo Dear Aerges.
I have another bug to report, please do not hate me. IFF in Mirage F1CE with "IFF mode 4 enabled for BE, CE, EE" in specials tab, becomes not clickable - however (that one is tricky) only in MP. In SP somehow it's a O.K.
Tomorrow I'll check the other versions of F1 if it's the same for them.
my best regards
Love your work guys. Thank you!
It seems to be linked with what the slot forced the IFF panel and the one that you selected in your special tab
-
On 1/13/2025 at 7:56 AM, Ski11B said:
So, first off, the Mirage is such an incredible mod. I love it, but for the life of me I cannot align the HUD nor the ADI or backup ADI. Please believe me when I say I've researched the hell out of this on the interwebs and have started up the jet, what seems like 10 different ways, according to reddit posts. It is so incredibly hard to fly the jet straight without constantly quickly gaining or losing altitude. The track I've attached is me starting the alignment with ground power only. But it doesn't matter how I align it because it turns out the same every time. Thank you in advance.
I don't understand, there is no HUD in the current versions available of the Mirage F1.
One or more cores reaching 100%
in Game Performance Bugs
Posted
I tested with a shortcut to DCS.exe with "--disable-features=UseEcoQoSForBackgroundProcess" and I got a 20fps improvement, still one thread at 100% on my 5800X3D, it occurs only on heavy scripted servers, rn testing on Greyflag Syria. On low scripted servers I have no CPU Bound (Render Thread) issue and running at 200fps.