All Activity

I'm back on DCS after some time off and I had to reinstall the game entirely (the patch was as big as the game, so my drive couldn't take the download on top of the already installed game). I'm not sure what setting I need to fix to have the mirrors stop looking horrible like that. I recall them being quite decent, but now it's ultra pixelated. I wasn't able to make Print Screen work or to take any screenshot, but trust me, it's really horrible.

The problem is that almost no servers list an F-16 on the REDFOR. Almost never happens .......Who cares about Mig-29s in BLUFOR. It would be the last choice after FA-18 or F-16.....REDFOR doesn't have an effective Fox 3 missile besides the SD-10. The R-77 is a total wasted of wing space...Very limited range, very easily defeated. Death spiral....

not a huge drawback not having a HMD in the daytime anyway since the light is often so bright it becomes difficult to see :). Since there's no HMD, will the gunsight reticle be more of a fictitious display or will it have a mechanical swing down arrangement like in the huey?

Have you considered that a given aircraft can fly on either "blue" or "red" sides? .. an F-16 can fly for REDFOR with a Venezuelan livery, a Mig-29 can fly for BLUEFOR with a luftwaffe livery, and so on. You are putting on your own force-jacket when setting up your coalition's countries, instead of using your imagination and devising mission situations that are balanced for both sides.

@mla306, another user just reported similar behaviour, and has same stack trace as you, in the Eagle Dynamics DCS Discord server bug forum. I've dropped your log and link to your post there as well if it helps them further. The user who posted there stated that this occurred for them in multiplayer, so not just this mission. The key thing they've highlighted, and they tested a few things, was that this occurred when asking George to switch to rockets... and the rockets are the M151 ones with the M433 Resistance Capacitance (RC) Fuze. Can you check in the mission editor for that mission 1 (you said the others were fine), if it's possible, to see what the weapons loadout is for that Apache to see if it's the same. If you can't access that in the mission editor yourself then post this info back to Stone Sky. Would recommend asking them anyway. If not the same rocket type and fuze then see what it is for you, ask Stone Sky if needed, and report back. I can pass this onto the other user and see if they can replicate with that loadout as well. I'll try this in the next few days myself as well.

Here is a summary of how to install DCS on Linux (Steam version): 1. Install protontricks with flatpak: https://github.com/flathub/com.github.Matoking.protontricks?tab=readme-ov-file#protontricks-for-flatpak This means you should install flatpak as described on the webpage before you install protontricks with the Linux terminal: flatpak install flathub com.github.Matoking.protontricks (It is recommended to use flatpak, because some Linux distros may not support newer protontricks versions required for the steam client.) 2. Add a few command prompt aliases: https://github.com/Matoking/protontricks?tab=readme-ov-file#flatpak-recommended echo "alias protontricks='flatpak run com.github.Matoking.protontricks'" >> ~/.bashrc echo "alias protontricks-launch='flatpak run --command=protontricks-launch com.github.Matoking.protontricks'" >> ~/.bashrc 3. Now you can follow the hoggit guide by running the command protontricks 223750 d3dcompiler_47 in the Linux terminal. In the launch option of the DCS steam properties you should add WINEDLLOVERRIDES='wbemprox=n' %command% or else DCS is not going to launch at all. 4. The DCS launcher does not run properly in Linux (you will see a black box on startup). In order to disable the launcher you need an editor to open the file "options.lua" in the install folder "Steam/steamapps/common/DCSWorld/MissionEditor/data/scripts" of DCS. Then you replace ["launcher"] = true with ["launcher"] = false 5. Start DCS in Steam. It should now run without getting stuck in an infinite loading loop.

OK, now everything is OK. I made a typo modifying ARK_MAIN_page.lua, now the plate report correctly names and callsigns. Configuring avionics as "native" and cockpit as "English" give the plate in Russian but all relevant cockpit labels in English. Thank you again for your support!

I truly hope that he is doing well.

Seems highly unlikely they'd form at typical wind over the deck speeds. If this were possible, with any carrier-borne aircraft, I'm sure we'd have seen photographic evidence.

@Calvin.Pimax...would you please comment about actions underway to find and fix this issue? Thanks.

Oh please let it be so.

I believe that Eagle Dynamics has set DCS into a death spiral because it does little to support REDFOR. They continue to develop and improve BLUFOR aircraft but provide nothing for them to fight against except AI. Plus they never actually complete any of the aircraft modules. They offer simplified versions of the SU-27 and J-11a with no modern Fox 3 missiles while constantly improving the AIM-120 and loading 10 of them onto an ever improving FA-18. The JF-17 is not a bad module but whenever the SD-10 get to good they dumb it down or break some other system on the aircraft. Many servers no longer even try to hide it. They don't even include REDFOR aircraft in their servers. DCS is destined to become a WWII sim or a PVE sim. They don't even try to get better. It is in a death spiral because it has no direct competition. One day a competitor will arrive and time will run out! Sorry for the rant.......

Brings hope and expectation of a big fat one coming in next time.

Should the vortexes even be visible at all?

I don't quite understand what any of those pictures really have to do with that. Could you perhaps elaborate that?

No patch for one month?

Maybe not in your house. In my house the flying is great fun. I flew yesterday and had fun. I'll fly tonight and have fun. And I'll fly tomorrow night and odds are I'll have fun again. Because flying in DCS is fun.

Nicht vor dem 30.September denn dann endet der Vorverkauf. Also wohl am 30.09. oder am 01.10.

Some things to try. 1. Did you try the config file I gave you in your other topic, the one with the displays table? 2. You do not need Helios for what you are trying to do, DCS will do that. We will need to modify the file for the RWR export, but let us see if we can get it working first. 3. You DO NOT need "Display Fusion" for what you are trying to do with DCS, turn it off or un-install it. Just Spacedesk for the iPad to work as another monitor. 4. Try moving your screens around in windows display settings, try these Enter resolution in DCS Main Settings = 5888x1536 Config file >>>>> 4wide.lua OR Enter resolution in DCS Main Settings = 3968x2160 Config file >>>>>4Z.lua 5. You pasted this above -- UIMainView = Viewports.Center UIMainView = { Gx = 0; <<<<<<<<<<<<<<<<<<<<<<<<<<<< ERROR, delete the G y = 0; width = 1920; height = 1080; }

if u want to change the plate to Russian but keep the cockpit in English,commenting out line 4 of the ARK_MAIN_page.lua doesn't work for me,but u can delete "TransliterateToLatDefault() " in line 150 and 163 of ARK_MAIN_page.lua ie :change UTF8_substring(TransliterateToLatDefault(ark_channel_data.name), 0, 15) UTF8_substring(TransliterateMorzeToLatDefault(ark_channel_data.callsign), 0, 6) to UTF8_substring(ark_channel_data.name, 0, 15) UTF8_substring(ark_channel_data.callsign, 0, 6) also the number behind it looks like name/callsign letter length limit(0,15 =max 15;0,6=max 6 letters) there are also some other lines but using LOCALIZE("")in that file,like the title of for the ADF plate,u can do the same to them if u want. like line 21, txt_main_caption.value = LOCALIZE("КАНАЛЫ АРК") >>editing>> txt_main_caption.value = "КАНАЛЫ АРК"

As @Aapje has said, the buttons and axes all work, and indeed the numbering is even the same, so in DCS you can just copy the Virpil column into the Moza column for each aircraft and you're good to go, but I would think any fancy programming you've got in the Virpil app will be lost unless the app can recognize inputs from other brand joysticks (the Virpil joystick tester app can). You could re-create your mini stick program in Joystick Gremlin for any brand of stick. Of all the flightsim stuff I've bought in recent years (and that's a lot), the Moza stick is the only thing I regret buying. It's a lovely piece of hardware but the software that drives it is truly terrible. I think that most of the glowing "game changer" reviews around the web are by people raving about the concept of FFB rather than the Moza specifically. My experience is that the Moza is only a slight upgrade from an old Sidewinder 2 which you can still find on Ebay for a tenth of the price.

Der Threadtitel in Kombination mit dem ersten Post ist verwirrend. Suchst du einfach nur etwas um die MFD zu bedienen? Dann gibt es was günstiges von Thrustmaster (Cougar) da habe ich sogar noch 4 Stück hier rumliegen. Was auch sehr gut funktioniert wenn du nicht VR fliegst und nicht unbedingt echte Schalter brauchst ist ein Streamdeck. null