All Activity

It is a very old feature. I meant, probably LOMAC old, that precedes our current image sharing services.

What I remember vividly from my visit there, which has been years ago at this point, is that videos do not do it proper justice usually, and it is sometimes more worthwhile to just enjoy the moment.

Even if you don't own them, that just mean that you can't pilot them, but you can still use them as AI units on your missions, to play as opposition or allied units.

Bump, as the canopy slider still doesn't seem to have any impact in quite a few modules afaik.

There are a lot of interesting options, but frankly, I doubt they are going for the angle of mainly maritime use helicopters anytime soon, considering that it would definitely increase the pressure of implementing ASW as a whole new topic, as well as the need to expand/modernise watery assets. Remember the 'year of naval focus'.

the pic posted by OP is CoreMods. when you join a server and fly against people, how will you see their AC represented? the CoreMods are all the official modules that DCS has.

Thank you for your insights and special thanks to Actium for having done the work to actually look into it. That answered my question. Yes, it does raise further questions, like... why? But lets not get carried away.

I’ve updated my original post to include the issues with the Pimax during night missions – it’s not quite perfect after all.

glad to help. good luck and clear skies.

Hey guys - quick update... I have now extensively tested the issues and adjustment options in a night mission (Syria, June, 4 a.m.) and a dawn mission (Syria, June, 04:15–04:30 a.m.): Problems: HALO around bright objects, especially the aircraft in external view Indefinable dark mass from the horizon downward; the transition from the stars over the horizon to the ground is not a clear line, but a constantly shifting “something” Partial “blackout”: when rotating the external view of the jet, brightness suddenly dims completely (across everything); when I then switch into the cockpit, everything is pitch black and the headset gradually brightens again Chromatic Aberration at sunrise / clouds, as described at the beginning of the thread Adjustment options: Contrast & Brightness in PP Local Dimming in PP Gamma in DCS Modifying the profile.json file as described by missioncmdr Upfront, everything that doesn’t work or has no effect: Problems: HALO does not go away, no matter what I do Horizon-to-ground transition remains undefinable Blackouts are still present Adjustment options: 2. Local Dimming in PP makes no difference 4. Modifying the profile.json (simply adding the line with the value, as it is not there initially) causes changes, but in my view nothing that Brightness couldn’t also achieve The only progress so far: Problem: 4. The Chromatic Aberration at sunrise or sunset on the horizon and in the clouds can be removed. Workaround: Set Brightness in PP to -2 and Gamma (previously 1.8 for me) to 2.8 (!). This results in beautifully smooth transitions without artifacts. I tried calibrating the correct brightness against the stars: everything I can see at B=0 and G=1.8, I can also see again at B=-2 and G=2.8. The problem then is with daytime missions: here, with B=-2, Gamma needs to be set to about 2.2–2.4, otherwise it looks too bright. You can fine-tune this a bit by setting Contrast to -2. Then Gamma can stay at 2.8 without affecting nighttime visuals, and during the day you get roughly the same brightness, although the colors appear a little more muted. On the other hand, Gamma can be changed during flight (for day/night missions). So – currently I’m using: In PP: Brightness -2 Contrast -2 In DCS: Gamma 2.8 Fun fact: If Pimax Play is completely closed and restarted, you still get the Chromatic Aberration despite Brightness -2 and Gamma 2.8. I need to briefly move the Brightness slider in PP, set it back to -2, hit Apply, and then the setting works again. This seems to be another bug. @Calvin.Pimax – please have your team take a look at this. It should all be solvable!

I've just noticed the same thing. 55gb of aircraft files I don't even own. It would be good if you could check a box for each livery you want installed per aircraft, even the ones you do own. Makes sense if you only want to play certain theatres and/or time periods.

Back in the day (2014 ish) I always had the impression through either MP chat or forum that "server allowed to take screenshots" was a measure on the person reporting a problem being able to snap a screenshot for the server side to check for the issue and not an anti cheat solution. In some situations it would cause server side performance issues if a person would spam the "print screen" button as the server is also receiving the shots on their end. I can be inaccurate because this memory is as fuzzy as it gets. I haven't been a multiplayer power user for many years now. Some interesting info from a quick google: "Server admin here- it's just a screencap of the game itself. I don't really know why it's even a thing. " "Most Multiplayer servers are taking screenshots from your aircraft in cool situations (e.g. sunset behind you or some stuff like that, dogfights and so on) and post them for example on their discord server for cool pictures. They ask you for permission to do that " Of course, some enlightenment about this feature from ED would be appreciated.

https://trudymai.ru/upload/iblock/99f/algoritm-kompleksnoy-sistemy-upravleniya-samoleta-mig29k_kub-v-rezhime-_dozapravka-toplivom-v-polete_.pdf?lang=ru&issue=45 paper on aspects of the flight control system

I'm thinking of purchasing a Moza AB9, but I've not been able to confidently figure out if I'm able to keep my axis to button mapping that I have set up for my Virpil Alpha. On the mini stick on the alpha, I currently have it configured in the vpc software to activate button pushes at 0% & 100% on each axis. Thus it can act like a hat switch. Is this possible in Moza software? Also is anyone able to confirm the brake axis works, and are all buttons recognised, can hats be set as 4way instead of 8?

I have the Virpil collective with throttle. Are you referring to the required action of using Pg Up and Pg Dn to rotate the throttle before it will accept your collective throttle input? That's been there since day one. It's become a habit for me to run it up and down prior to starting up. I'm also now seeing a problem with it starting up at the Idle-Cut Off position but at full rpm, which it didn't do before. It used to start at a lower rpm until you advanced the throttle to max. However, I believe the old work around was to push the Idle-Cut Off button on the sim's collective (not on your controller) and run it up and down to set the Idle-Cut Off position in the sim's memory (or something like that). But, here's a proposed fix:

@BunnyKeeper As briefed he will remain in formation, he will not refuel. He also will not run out of fuel. That is the problem, when commanding him to refuel thats when intermittently he goes AWOL. Cheers

Fixed . https://github.com/landre-cerp/McduDcsBiosBridge/releases Cdu knobs on center panel controls the Backlight of the screen / leds / keys . ** Looks like in the Aircraft , Backlight is not controlled by the Rocker BRT DIM either ? so i decided to link it to the knob ** . Should it be corrected one day , i'll separate them .

Excellent idea: I hope we'll have some good news soon. The Colmar and Strasbourg bases are really eagerly awaited by French players (in the absence of Orange, Dijon, or Cambrai... to name just a few ).

Being privacy minded and out of curiosity, I had a look at the WebGUI, which is used to create said screenshots. At first, the screenshot function seems defunct. Note the broken image icon that appeared after trying to take a screenshot via the camera button: Took a closer look with the Web Developer Tools (F12). The HTTP GET request, which is supposed to retrieve the screenshot from the dedicated server, fails with Error 404 (Not Found). However, the URL http://127.0.0.1:8088/screenshots//screenshots/d7GSsJF1dg6hbrm looks wonky, judging from the double slash between the two occurrences of screenshot. Won't bother to file a bug report for that, as that seems to be a waste of time. Change that to http://127.0.0.1:8088/screenshots/d7GSsJF1dg6hbrm and you'll get an actual screenshot, which appears to be limited to whatever is rendered by DCS itself. I disabled full-screen mode, put a bunch of windows on top of the DCS window, took a screenshot, and got this (lacks all the stacked windows):

I meant checking my channel/site to understand why AI is used in the first place. Ergo, the article I posted or other similar comments. I haven't even read the previous posts on this topic and, had it not been reported to my attention by a friend of mine, I would have missed it entirely. Again, little time, too many things to check. I'm glad you like researching and better understand various aspects of this world. It is what I enjoy the most, since I have not been able to commit 3h to fly a proper mission since 2020. Btw, if you have accounts, ideally from both sides, I am more than happy to post them on the website and credit them to you. The best thing to do with knowledge is sharing it. Happy to continue, but admittedly still unhappy about being labelled so easily

The R-3350 isn't remotely a comparable example to the R-2800. The 3350 suffered numerous problems inherent within its design (including the use of flammable magnesium components, bad cylinder head design,excessively lean fuel-air mix, etc.) because of a rushed production cycle. The cooling issues were only part of the problem. The R-2800 didn't have those problems. It was an engine that could LITERALLY have whole cylinder heads blown off and still get the plane home again.

Ok, I will accept it is not generated by the AI. With proliferation of AI and no direct statement from ED, I had genuine concern which Nineline clarified. It's true: I did go over the line here. But I also think ED should have spoken directly on this topic. I will not comment on contnet of your youtube further, and I am sorry for leaving you feel labeled and angry. On my side I assure you that I did spend large amount of my time researching the topic of 29 flights in 1999. I did try to find out as much as I could, especially due to the fact that the pilots did experience problems whenever they tried to speak out. 26 years after the events we are still learning knew facts and each interview of the pilots from both sides provides additional information. Unlike propaganda narration of media on both sides, I found out that the interviews of the pilots largely matched each other, and that as humans they do respect each other. In some cases I did find out that: parts of their statements were departing from the actually state on the ground, sometimes they avoided telling everything. I would prefer not to use word lie, but simply they can not share everything with us. Each story is time-stamped so English and Serbian speakers can listen themselves potentiality comment on accuracy of translation or provide additional information (reason why forum was chosen in the first place). For each story I provided additional sources(e.g. crosschecked with other branches like VOJIN/EWR) and all information, to my best knowledge are public information with no confidential data. Overall it has been a very satisfying experience for me, I do not feel the effort is wasted. So answer is clear I did do my homework when researching the topic. Your comments are welcome. I do work full time, have a family, go on vacation, and probably do all the things you do as well, and just like you I like having this hobby, and have used my free time and precious vacation days to e.g. visit newspaper archive for one of these stories. If this answer satisfies you I would rather place this topic back to the original track. That said: how do we match the reality with simulated?

The course setting only affects the command steering symbol, not the LOC/GP bars in the HUD/ADI.