All Activity

If you haven’t heard back from our support team regarding the replacement or any workaround for the jittering issue, feel free to ping me. You can export the log files from Pimax Play and send them to edgar.chen@pimax.com—he’s our engineer in charge for SLAM tracking project.

No sound in multiplayer. How can I fix this? Digital Combat Simulator Black Shark 2025.09.10 - 11.51.48.02.mp4

That's not true. F-16C Baltic Dragon.zip livery uses 55MB space, unpacked it's 278MB. Other liveries yield to similar ratios. But ok, question answered by @Czar. I was just curious why DCS downloads a lot of liveries in .zip format when updating and thought it might be a space saving option.

Reported back to our devs, and they are looking into it now.

Thanks for your replay. Ah ok....

Is the flight model the same?

Hallo Blackwood Schau dich mal bei Tek Creations um, da solltest du was passendes und nicht allzu teures finden. Winwing ist auch zu empfehlen, aber ausser dem ICP haben die nicht viel mehr für die F-16.

ordered the MCDU from WinWing Get ready to be bothered with stupid questions on how to set it up with the CH47 and later the C130

Thank you. I primarily focus on creating skins for vanilla modules, so I'm holding off on mod skins for now. While I'd like to create skins for aircraft like the F-16D and F/A-18E/F, I want to keep the barrier to entry for skin implementation as low as possible, especially considering multiplayer environments.

Классно выглядит. Видно - с любовью сделано. Такой авионики у нас еще не было. Уже не истребитель, но и не совсем авиалайнер. Интересно, будут ли делать версию для MSFS.

Perhaps @Diesel_Thunder knows?

I took advantage of advice more than I gave it. But I have at heart to answer each time. Christian

Great work! Any plans for something similar for the IDF mods Project F-16Ds?

Hmm, ok, I used the Forrestal as reference, and there they are lit. Any reference that shows how the Enterprise should properly look at night? On Work in Progress, yeah, of course we are aware of the many imperfections and while we aim to resolve most of them, realistically we will never be able to fix them all... Cheers, TeTeT

То есть луч не то чтобы постоянно светит в задницу ракете, но периодически в нее попадает и по параметрам принимаемого задницей излучения ракета понимает насколько она отклонена от линии прицеливания и корректирует полет соотвественно. Если же находится в центре - не корректирует.

Nope, no mods, no addons except SRS which only runs while connected to MP Servers. Strange...

Да вот, соседняя тема. Там про ЛЛКУ написано.

Hallo zusammen. Ich bin auf der Suche nach einigen Button-Boxen für die F-16C. Hatte bereits selber an das Bauen mit Arduino gedacht, aber leider funktioniert das alles nicht so, wie ich es mir gedacht habe. Nun fand ich Etsy und dachte mir: „Wow, hier gibt es das, was ich gebrauchen könnte.“ Allerdings fand ich dann auch die Bewertungen über das Geschäft und das gefiel mir ganz und gar nicht. Kann mir jemand mitteilen, ob es da nicht noch etwas anderes gibt, das zudem auch nicht so überteuert ist? Würde mich freuen, wenn jemand etwas weiß und dieses mir mitteilt. Danke euch..

For COs - I meant Cycling Ops. CQ - Carrier Quals (qualifications). Squadron altitude is the stack alt established for your squad before the flight.

The Moza configuration capability basically replaces the Virpil config software. So any clever configurations that you might have had are unlikely to work. I don't remember seeing any way to reconfigure the hat as buttons (please do correct me if I'm wrong on that). One of the implications being that you'll need to rebind every command for every aircraft within DCS for the Moza Whilst that's somewhat annoying, I've had mine for a number of months now and love it. I've kept my Virpil T50 base and Alpha for the time being "just in case", as the Moza is a lot more complex because of it's motors, and therefore is unlikely to be as reliable. I've never wanted to go back to the pure Virpil solution. Yes, the initial setup is a PITA, but once you figure out basic usage, the AB9 really is a game changer. Ref config, there are some out of the box pre-configured profiles. They're a good starting point. Once you get a feel for what you want, you can start creating new profiles, specific for an aircraft type, with tailored settings. Currently, all of my profiles use Telemetry data and have all of the individual settings enabled, with the profiles for each setting modified as I wish. So for example, in the Huey, I've lightened the spring and dampers, so that it has far less resistance. As I've never flown anything, and have never seen much on the specific feel of a real aircraft, I'm just guessing, but over time, they're coming together. Some interesting oddities: All of the default profiles were using "Integrated" to collate feedback data from DCS. As I understand it, this combines both the telemetry data from DCS AND the FFB data from DCS. It's not nice. Hence why I set mine to telemetry only. Maybe the FFB data from DCS will in the future be good enough to replace the telemetry, but right now, I don't use it The damage setting is by default disabled for all of the profiles. It's very easy to enable, just a single tick, but it does mean checking every profile The default gun recoil on say the Hind is absolutely nuts. That required a bit more finesse on the curve Where there is no obvious profile for an aircraft, just copy one that's similar, assign that to work with the aircraft that you'll be using, and then further refine. Doesn't take long once you get the hang of it Moza do state compatibility, but with only a limited number of grips, the Alpha being one of them. It does work with the Alpha Prime that I bought a few months ago. However (of course), Virpil updated the configuration such that out of the box, the flip trigger is seen as two buttons. That wasn't the case within the Virpil software with the Alpha. Sure enough, that means that moving from the Alpha to the Alpha Prime required re-binding EVERY CONTROL for EVERY AIRCRAFT again (joy). Again, I can't complain too much, as whilst the Prime isn't really that different to the Alpha, I do love the feel of it. It's not really worth the cost to upgrade, but hey, what the hell.

Thank you. Just a couple of clarifications please. COs = commanding officer? Meaning what with regard to my question? And what is "squadron altitude"?

This is video was very well made and it is the confirmation that this module brings quality and completeness. They have even worked the full functionalities of the AMU and from what I saw on the previous video the CNI-MU is also fully implemented and this is easier to say that actually doing it. If it would have not been that I have already pre-purchase it the first day it was available, I would purchase it right now. I can see an incredible potential for missions and since the Airplane Company was "new" on DCS I was a bit cautious on this but seeing what we have seen on the provided videos I LOVE IT, another great third party developer that knows how to do its job !!!

The Kandahar Firing Ranges training mission has been updated in user files: added Texas Helo Range for rotary wings; removed High Digit SAM mod, the mission is now mod-free. More details about Tarnak Range here, and Texas Helo Range there (external links).

For comfort check Globular Cluster Comfort Mod. For audio check Globular Cluster PH2 phones. Colors are exceptional good, these panels are 10-Bit capable (HDR). Resolution is a bit less than G2, but the FOV is much bigger(!!!). Also check my DFR settings file for Quad Views, you can boost sharpness by a huge amount. Binocular overlap is also pretty good so depth perception will be too. Performance is dependent on your system. I recommend to let the panels run in 120Hz mode and SteamVR global SS setting 150%. Rest is tuning the game and what your GPU has to offer (DLSS 4 performance mode, profile K etc.). One very important aspect is IPD setting and finding the right position on your head. The Globular Cluster Mod helps with this. But if you don't own a PS5 you can't take advantage of the IPD measuring and calibration via eye tracking (not yet?!). Finding the right values might take some time.

My setup in windows is exactly like in post above,and i have display fusion utility which handles monitor setup with a use of a profile with 4 monitors - that screen with number 3 is from my ipad, and i use mfd cougar taped to an ipad air2 which has native resolution which is 2048x1536 - if i change it to resolution to that one of other monitors which is 1920*1080 i will mess my ampcd export for f-18...That left side that is not aligned to rest of monitors is of not use for my export needs...Only if this setup messes with dcs positioning main screen on largest resolution monitor? My monitor.lua and resolution in dcs are all setup right, because when it was working i got all mfds exported in right position...something changed and i don't know what, when i am away for a few months from dcs and when i get back again my export is all messed up. And here is my monitor.lua _ = function(p) return p end name = _('H_0-HR_F18_4-screens') description = 'Generated from Helios Profile 0 - HR_F18_ 4-screens' CENTER_MFCD = { x = 720, y = 2496, width = 1200, height = 1200 } FA_18C_RWR = { x = 322, y = 3395, width = 214, height = 211 } LEFT_MFCD = { x = 0, y = 1082, width = 850, height = 850 } RIGHT_MFCD = { x = 1070, y = 1082, width = 850, height = 850 } Viewports = { Center = { x = 0, y = 0, width = 1920, height = 1080, aspect = 1.77777777777778, dx = 0, dy = 0 } } -- UIMainView = Viewports.Center UIMainView = { Gx = 0; y = 0; width = 1920; height = 1080; } GU_Main_VIEWPORT = { x = 0; y = 0; width = 1920; height = 1080; } null