All Activity

That's the next hurdle I'm looking into. Head tracking in Linux exists via OpenTrack: https://github.com/opentrack/opentrack As for VR, this guy appears to have got VR working in DCS and Linux but I suspect this will be specific to VR make and model:

I dont fully follow your example. The system saves the entire aircraft state, all its 3000+ properties. That doesnt just include wear/tear but also literal state. For example if you turned the laser on or the position of the lense inside the Pave Spike camera or whether a lamp is currently on or not etc. Wear/Tear never reaches a state where something doesnt work anymore. That would be failures and those are decoupled from wear/tear and automatically repaired across missions. Your aircraft with maximum wear/tear will still work, it just will be a rough experience and performance of all components will deviate a lot from what they are expected to be (in both directions, underperform but also overperform). Details to the wear/tear system in the manual.

@SimHog Damn, that's interesting! Sent from my SM-A536B using Tapatalk Seems we're getting closer. What about VoiceAttack/VAICOM with WhisperAttack. That's a game breaker for me!

Release Version Current version number: DCS hotfix 2.9.21.16552 Next planned update: To be announced

Better to ask one of the DLC campaign creators like @Reflected. I think his liveries are included in the missions. But I could be wrong and they're included in the Core. I for sure has never downloaded any liveries before playing his campaigns. Cheers! Sent from my SM-A536B using Tapatalk

Nothing for the Mig29?! No working Radio altimeter or VVI nor getting back the english labels?

Are you using any kind of head tracking or VR? If so, how does that work under Linux?

Watching Wags’ videos mid-flight sounds like peak multitasking.

I haven't quite figured out the state-saving function of the aircraft. Does this function save wear or only the condition of the switches in the airplane? If the aircraft wears out, how can it be repaired?For example, it saves the Squawk Code, which I made for convenience. like the aircraft number 426. But it doesn't save 426. It saves 422. It's not essential, but I don't understand everything yet. I have "enabled" in the advanced settings and sometimes I do RCtrl+P.

Nope. Alt Tab, Win D, Win Tab, Win arrows do not work. The splash screen is extremely resistant.

Turns out WinBoat wasn't needed at all. I'm currently using Bazzite v42 and DCS World runs fine on Lutris and it recognises my WinWing HOTAS and Skywalker pedals without any issues. There is mention online that Linux is limited to 80 buttons however that limit only applies to older kernel versions ** apprently **. I'm still looking into this. If it helps anyone, Bazzite is a fork of Fedora, you can install the fedora joystick-support package using the rpm-ostree package system via command terminal: rpm-ostree install joystick-support Also I'm getting better FPS than I was on Win11

https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.21.16552/ DCS Core Hotfix for several certain cases of crashes with modules like Mi-24P, F-14, induced by changes from last update. Password protected slots cannot be occupied by a player in the Multiplayer - Fixed. Campaigns DCS: F/A-18C & DCS: F-14 Iron Tide Campaign by Sandman Simulations All mission: CAP and escort flight behavior changed to prevent flights leaving the designated area of operations. Wind speed changes to make sure flights use Ramat David runway 33.

https://www.digitalcombatsimulator.com/en/news/changelog/release/2.9.21.16552/ DCS Core Hotfix for several certain cases of crashes with modules like Mi-24P, F-14, induced by changes from last update. Password protected slots cannot be occupied by a player in the Multiplayer - Fixed. Campaigns DCS: F/A-18C & DCS: F-14 Iron Tide Campaign by Sandman Simulations All mission: CAP and escort flight behavior changed to prevent flights leaving the designated area of operations. Wind speed changes to make sure flights use Ramat David runway 33.

Doesn't Alt+Tab work for you guys?

There's a ton of conflicting sources around that mix the P/PT and the PS/PM so it's always been hard for me to find what the truth is on the PS. The most common statements i've seen is that the 5V55R used on the PS/PM is always specified as only SARH, and not command-SARH or command-TVM. If you have more direct sources or even first party ones i'd love to add them to my collection. Using TVM affords you more flexibility in the waveforms that you can use which could or could not preclude RWR systems from keying on launches. For example again the APG-73, its PDI mode is a different CPI to CPI waveform than HPRF track and RGHPRF used in search. It's likely a single adaptive PRF and close to 50% duty cycle while only ranging based doppler frequency. Supplimented with periodic burst ranging to keep range estimation errors in line that can accumulate. Once an AIM-7 is fired it ceases all burst ranging because the sparrow has to have uninterrupted HPRF pulses to home in on. You don't have this limitation TVM and do more with it, you can keep your waveforms similar between track and launch without it being detectable as one by warning receivers. It also means you can do more things to hide your uplink from being detected. Yes, if it can detect either the radar mode change or the datalink, it'll detect launch. If it cant detect either then it cant detect launch at all. The research just needs to be done on the systems in question to get specifics on how each mode operates or get specifics of the waveforms. I think you're misinterpreting things. That document does say those things, but they say it in 2 separate places not together and i think you're making conclusion to 1 based off the other. I'm not convinced the TVM array does the target illumination but instead it handles the up and down link separately so the main array doesnt have to interrupt its interlieved search/track/target illumination tasks, which is a very time-energy intesive task as it has to be continuous and be extremely rapid in update rates. The fact that the TVM array is a fraction of the size of the main array would suggest this to be the case as well. SM-2 doesn't use TVM guidance so not sure why that's being brought up, under AEGIS scheme its command-SARH while others use the 2T scheme with command/inertial-SARH. SPY tracks the interceptors for acceleration command computations and the uplink is a whole separate array task with an FSK encoded waveform. You missed the point i made. The search, track and PDI waveforms for the APG-73 are in fact different and there is reasons for it. It's the whole reason why i gave it as an example as to why you cant make the conclusion that PD illuminated sparrows are all undetectable launches. HPRF search is 2 PRFs with FMR and high duty cycle but lower than HPRF track, HPRF track is 4 PRFs at high duty cycle and no FMR with periodic HPRF or MRF burst ranging, HPRF PDI is single adaptive PRF to keep the target out of eclipsing zones and no burst ranging. A sufficiently modern RWR system could absolutely identify each one of these stages and trigger launch warning based on switch to PDI. There is nothing advanced about a PSK/QPSK uplink to make it undetectable. The amraam's datalink is going to be constrained by the requirements of the data message format and bit encoding while having cross-compatibility across a huge variety of launch platforms all with different radars built to different requirements. There isn't any room building in LPI characteristics. Its datalink is made more or less interceptable by how that datalink is used across different platforms. The hornets is less interceptable because the encoding happens within the same HPRF pulses its sending out for target detection/tracking in any search or track mode, making whatever identified mode it is pretty much irrelevant. This is a big point because if you design your RWR system to trigger launch warnings just on the presence of a detected datalink and nothing else, there will be a ton of false positives and the the usefulness of the system to provide adequete SA to the pilot will be very degraded. As seen by those F-4's in vietnam that had no indication of whether that datalink signal was it alone or if there was also a CW signal from the track radar.

Superstition can be really annoying.

what was your prompt into chatgpt ?

Hi bist du auf Discord bei DCS, du kannst ja mal das log dort hochladen (dcs-log-analyzer)

Can we at least get the Phimat as ballast to counter the weight for the Barax please?

Excellent! And again, thanks a lot for the hard work, really looking forward to this!

I also thought it would be possible, because I had seen skins I don´t remember installing before playing a mission in multiplayer. So, if you know how it´s done, could please you be so kind to tell me?

Hello Chuck, do you plan to make a guide on the OH-58D Kiowa?

The only information we have at the moment, is that Razbam modules will continue to work throughout 2.9.X If you read between the lines, that basically means support is running on its last legs, and the modules will either have serious issues or stop working altogether in 3.0.X (there likely won't be 2.10.X) - unless something changes and the dispute is resolved with an outcome that benefits end-users who are owners of the modules.

I wouldn't dwell too much on Spitfire parameters as a base for Mossie tweaks. The former doesn't have tyre spring and damper properties simulation of the latter implemented, plus we don't know how the difference between rubber stack of Mossie gear is simulated vs gas/oleo gear in all other DCS warbirds. Not to mention lines which might be coding leftovers not used in simulation at all.

Absolutely. Indifference, Ignorance and unawareness (and to a lesser extent inability) is a big part of the problem. As it is in every issue, be it politics or anything. But precisely for that reason it is important that those that are at least somewhat capable and knowledgable fight back as hard as possible.