1Arc

Does this have anything to do with it not loading in?

To be fair, I had my cursor toggle (which I rebound to "=") not working, while the default bind LAlt + C still worked. I found it a bit strange since in my keybind it did have "LAlt + C; =" and when readding "=" to the bind I didn't remember if it says "=" is in use with another keybind. This happened just few days ago after the Feb 2024 patch, on which before I did rebind a lot of keys when BE keybinds were introduced. Just a heads up if anything didn't go as planned. Cheers.

[Just posting this here to officially insert it to the list] At current state, using non-axis method of throttle control is very sluggish, that takes over 5 seconds for full range throttle movement, over twice the time required for most other modules. This makes it uncomfortably takes a while to do quick adjustment, such as in go around, AAR, and some others. Currently the only method to "adjust" this setting is by Afterburner Detent Setting, where it squeezes the rate if it's decreased (makes the mil power movement a lot smoother, but at the expense of getting in and out AB a lot slower) and vice versa. Videos attached show how different AB detent settings affect non-axis throttle movement, although it was recorded on older patch the effect is still the same to this day as of writing. I think this addition could really helps in term on Quality of Life for non full throttle user, especially for travelling setup when using controller or others (mouse side buttons for my setup). Cheers. 15E Test ABD 35.mp4 15E Test ABD 90.mp4

Currently, there are several RWR symbologies that's missing from root library, so far that I've found: - MiG-29G - FPS-117 Dome - HMS Invincible - Silkworm SR - Modded aircraft (if you use one) With AN_PRG45.lua and NCTR.lua (Mirage F1s and MiG-29G are not in default NCTR database) being editable, I'd like to see the RWR library to also be editable from there (i.e. SERVAL.lua) to fill in the blanks/Unknowns, as the dcs log also gives info if the unknows are detected.

Ignore this ^^ Got the fix that I wanted, and the solution I refused from the start. Rename Saved Games\DCS to something else and it generates a new one that somehow fixed the previous problem, somehow. UPDATE: After several test and playing around with individual mods I've concluded that one of these mods that I used for template setup might be the culprit, removed three of them at the same time and my game back as normal, so unknown which one: - SK60 [Not tested in detail] - JAS39 [Confirmed by DragonOfTheArmory] - Su-30 [Confirmed Cause] (thanks Nawi414) - T45 [Probably/Most likely] (tested on server) - VSN F-104 [Not tested in detail] (was removed in tandem with T45, unsure) Some mods that me and friend tested safe so far: - A-4E - Hercules Anubis - UH-60L - OV-10 Bronco - VSN YF-12 (Nawi414) - VSN F-4 with symptomps of occurance based on my few testing as follow: - JSOW directly hitting target - Fused bombs not exploding and CBUs not dispensing - APCs and Tanks (and probably more) placed in ME will not exist when said mission is entered - Carriers gone - LGBs ignoring laser designation Test platform used: F14A/B, F15E, F18C, Client ME, Server

Just noticed this problem when I was testing GBU-31v3B on F-15E that they're not exploding after impact (which before 2023 12 19 patch it did), and this also extends to 15E JSOW which somehow prefer to hit its target directly rather than deploying bomblets (even if higher alt was set the JSOW would just nosedive after passing target). After a while I noticed this problem also presents with the conventional CBU, where they don't burst but instead just disappear couple of meters above the ground. After more testing with Mk.20 which I could compare cross module (14 and 15E), all of them showed this same behavior, of which just going dud. Couple of things I've done was: - Temporarily removed my installed mods from Saved Games folder - Uninstalled and reinstalled F-15E module - Re-verify my games on steam Any help would be appreciated. Here's a track of me dropping Mk.20 on 14 and 15E, which on my end none of them opened up. SomethingWrong.trk

Hi there, also using non axis input for throttle movement in 15E. I do agree it's super excessive, and honestly took a lot enjoyment over flying other aircrafts currently (others being approximately 2-2.5 secs for time range of throttle movement). I've hit RB Maple to look forward for this issue a while back, still haven't got anything yet sadly. The only setting I could meddle with to tune this is just by playing around with the AB detent cutoff setting, lower means more seamless movement in mil power at cost of AB throttle movement taking forever. It does come with AB desync when flying in multicrew with someone else at different AB cutoff setting though. I've yet to find any way to mess with the rate within the script though, and really wish this could be one of the top QoL priority (either smoothen it or just make a rate slider in the special option). Some reference chart if you want to tweak the AB detent yourself.

For now try to make sure file name references in description.lua files are correct to the corresponding ones, mine are working file with the latest change only on dynamic tail numbering.

Aight, thanks.

Just found out recently, and managed to replicate it multiple time in both A and B by pulling the stick and sometimes when the cat starts to jitter my view bugged such as in screenshots listed below (screen zoomed and stretched). Sometimes it doesn't, and I'm not using head tracking device.

Fixed with value of 0.8, somehow value of 0.5 still shows tail number. nullIf dynamic number on the side of the cockpit if possible I'd like to know it. " custom_args = { [850] = 0.8, -- turn on/off vertical tail dynamic numbers (< 0.5 is on) }"

It seems the new Viggen tactical number update not only affecting my unnumbered liveries.

Having an identity crisis.

Honestly it was, my clan server suddenly had it active after update without any clear option how to disable it. Dunno what my friend did but thank god it could be disabled, and I no longer get kicked for entering viggen.

"It is possible yes. The order required is to first enable this cockpit mod, and then the EP08 one. Be aware though that the EP08 will fail texture IC." Although I still use it and tank the pain of having to restart (assuming the server not requiring pure texture). Hopefully with the new update later on it'll be integrated within vanilla release.

It seems our prayers have been heard. Either way time to celebrate, skål!!

How it's currently here even without loading the cartridge (9099) your starting airport will be assigned to LS and L1. Some however, especially in non-conventional airport start (ex: short air base operation instant action which starts in near kutaisi, would need cartridge to be loaded or even airbase code inputted manually. This all comes back to how the mission was setup. If the airstrip is not in the airbase code, well it manually inputting coordinate and runway heading. Unless I'm planning a complex route I nowadays just got lazy and inputted 1-3 waypoints manually.

Viggen 2.8?? One can hope, I truly adore these.

I don't know if this was a thing, but yeah you can't load viggen with these mods in server with "pure texture" and "pure script" (if script section modified) as it'll just kick you once viggen is loaded. Never know nor noticed since before 2.8 I've never been kicked or flagged for having viggen mods loaded for the "pure texture" setting.

I'm currently playing AJS-37 with MYSE's mod collections and IC's been acting up since the new "pure script" IC in 2.8. I can't say for certain what does and doesn't trigger IC check to fail (even in server that doesn't use pure script IC), but I get consistent result after entering and quitting any single player missions. As for being kicked for tainted client while playing in a server or after leaving a server, rarely it happen yet sometimes not. That's my situation for now. Addition: Apparently "Requires Pure Texture" is partly to blame as in a server with that setting on I've only been flagged once I entered Viggen with modded cockpits, EP08, HUD, and RWR.

A bit sad, now got flagged after 2.8

As for now the "F14 Clean Label Cockpits" is your best friend: https://www.digitalcombatsimulator.com/en/files/3303911/ Enjoy.

nullYes. I have no idea how to make any of them shoot off from the pylons, maybe just for photos and stuffs. Might soon gonna get lynched for this monstrosity.

Hello, In my opinion keyboard control for Mirage F1 is just not sensitive enough, yes it's sensitive enough to enjoy flying and dogfighting, however the lack of sensitivity is very apparent with rudder control. Which means it's kinda annoying for taxiing with current rudder sensitivity as it requires second or two for rudder input to show some effect, and of course one of the most affected part in flight is for high AoA maneuvers and stall/spin recovery. Slow respond for roll input also makes uncomfortable flight after firing sidewinder/550 or 530, and slow return to center messes with some maneuver (especially at very low altitude). Could sensitivity control option be added at least in the special menu for F1 to configure the sensitivity of rudder, pitch, and roll input using keyboard? No, "get HOTAS/HOSAS" no go for me. Any other recommendation for meddling with these sensitivity within game folders is also appreciated since it also could help me configure other aircrafts. For reference, I've included recording, a bit scuffed but it's basically what I can record with the setup. Any help appreciated, thanks.