unknown

Sorry for OT but i was not following the MSFS development much but i just read it will not support VR? Maybe after release they say? Wow, so there is zero reason for me to even test that thing.

Haha, i saw the same comment and came here to have a look if somebody already have this reported. :megalol::thumbup: Now i'm intrigued if the next Wags video over Syria is in an Mi-24 :shocking::hehe::shifty:

If my memory serves me well it was also called Mirage 2000C in the ED shop, but was renamed DCS M2000C. Asked why the rebranding in the shop there was a response like "We know it's a Mirage, Dassault knows it's a Mirage...." but it was not allowed to be selled under the name Mirage. If this has changed after Razbam worked with AdA :dunno:

I don't wait for sales. Actually i only bought one thing during a sale, a paid campaign for the MI-8. I wish you much fun with MSFS, seriously. But MSFS interests me zero, if they release a MSCFS i will have a look :D but before that happens, no thank you MS.

I don't get the complaining about sales....you got this summer sale, before that the corona sale(how many weeks lasted that one?) including free trail periodes for nearly all modules and even with 50%off for modules only recently released(that f*cked every F-16 EA buyer hard ;) ). And that wasn't the first sale this year neither.... so just wait a month or two and you will see the next sale event. Is it poorly handled from ED to say the sale ends on time x and later they say it ends on time y? Yes, but who cares, the next sale is for sure around the corner for you guys :music_whistling:

There were several lighting issues in DCS where you had to play with the gamma to compensate. I was running 1.7(like Wags) and 1.9 for a long time. After reading from HB that all their artwork is calibrated to 2.2 i used that and found for myself that i don't suffer the lighting problems anymore(cockpits!). ED changed something with 2.5.6 again(talking about terrain/haze) but every cockpit works/looks absolutly fine with a 2.2 Gamma despite what imacken says "A gamma of 2.2 will of course, lighten up the cockpit, but it blows the terrains and every other module pit out completely." -> i can't confirm this on my end. Fun "fact" for me/on my side i only see this "problem" imacken is talking about if i lower my gamma to 1.5 or even lower! With 1.6 or above i have no problem seeing that described switch in the Mirage cockpit, he also never said what gamma setting he is using in DCS. But who cares, he said the problem must be tied to shadows setting to high(his pictures), i tested with shadows medium/high and had no problems. He has his opinion about it, i have mine and i think he and i will agree that we will disagree about that topic. Thats fine for me, because everybody can test for himself and make up his mind. :thumbup: :beer:

OK, then i don't get it. You say you have to crank up the gamma to see the switch and turn it back to "normal", but normal in DCS is 2.2 and for that value all developers "calibrate" their artwork for their PBR materials. And then you tell me 2.2 is way to high and "blows the terrains and every other modules pit out completely". So you don't use the DCS normal value it seems. While i can partly agree with the terrain issue i can't agree with the other modules cockpits, they are all perfectly fine with gamma set to 2.2. And lowering the gamma to 1.9 or 2.0 on my side "fixes" the "blows the terrains..." part for me if i want it a little darker without cousing any visibility issues in any module for me. Yes, i compared shadows med/high because you said: that you have no problems with shadow=off but with shadows=high. And i can't reproduce this on my end because i use shadows=med for VR performance and testet with shadows=high to see if i can reproduce the "problem" and i couldn't, so i posted my results. Works fine in VR and on my monitor with a gamma of 2.2 and the only way i can reproduce this is by lowering the gamma to 1.5 or lower, so i agree here with jojo that it looks like wrong calibrated monitor/gamma settings for me if you encounter this problem. :beer:

Tbh i can't understand/reproduce the "dark cockpit problem" anymore after the cockpit rework. Before that rework i would agree but after....looks fine for me. I use a Gamma of 2.2(DCS default?) because HB said thats (physical/PBR?) correct and all their artwork is done for that gamma value. Attached are two pictures, first with shadows on medium and the second with shadows at high(also turned the Mirage so the shadows in cockpit are the darkest), i use medium because for VR performance reasons, and i have no problems with a dark cockpit. Mirage2k Caucasus FreeFlight IA mission. To get my cockpit as dark as in imacken's picture i have to reduce my gamma to 1.5 or lower.

Thank you again for your kind help, Спасибо! :beer:

I would use my VR hand controller(s) for everything i have not mapped to my HOTAS like i do in every module. Also you can use your VR hand controller already in some modules to fly them(grab and use stick/throttle), so it could be the perfect VR module.

Yeah, looks fine for me too. https://www.alamy.de/stockfoto-syrien-morgen-verkehr-auf-breiten-beirut-avenue-im-modernen-teil-von-damaskus-19051612.html?pv=1&stamp=2&imageid=6AF20FDD-FC15-401E-9369-F56976AF934B&p=7013&n=0&orientation=0&pn=1&searchtype=0&IsFromSearch=1&srch=foo%3dbar%26st%3d0%26pn%3d1%26ps%3d100%26sortby%3d2%26resultview%3dsortbyPopular%26npgs%3d0%26qt%3ddamascus%26qt_raw%3ddamaskus%26lic%3d3%26mr%3d0%26pr%3d0%26ot%3d0%26creative%3d%26ag%3d0%26hc%3d0%26pc%3d%26blackwhite%3d%26cutout%3d%26tbar%3d1%26et%3d0x000000000000000000000%26vp%3d0%26loc%3d0%26imgt%3d0%26dtfr%3d%26dtto%3d%26size%3d0xFF%26archive%3d1%26groupid%3d%26pseudoid%3d%26a%3d%26cdid%3d%26cdsrt%3d%26name%3d%26qn%3d%26apalib%3d%26apalic%3d%26lightbox%3d%26gname%3d%26gtype%3d%26xstx%3d0%26simid%3d%26saveQry%3d%26editorial%3d1%26nu%3d%26t%3d%26edoptin%3d%26customgeoip%3d%26cap%3d1%26cbstore%3d1%26vd%3d0%26lb%3d%26fi%3d2%26edrf%3d%26ispremium%3d1%26flip%3d0%26pl%3d

It's sitting cold on the ramp, how can you evaluate the progress on system coding? :D ;)

I'm so happy this is the first sentence of the announcement....FREE....so nobody can scream i paid for it and i demand..... It's a free for all AI asset, nobody cares if it is released 1 day after the announcement or 100 years. Tbh, just cancel the project and make it a full DCS module instead! :D ;)

+1 I wait for the "Oh, what is this Apache doing here" moment (copyright by Wags ;) ) before i get excited.

Subject of the topic Igla i bought the book "MIL Mi-24 Attack Helicoper". There is a topic AA missiles, stating that first Strela and later Igla missiles were fitted to MI-24s but both weren't used in large scale probably of inadequate missile(seeker?) range. "...probably because the more modern Ataka-V and Shturm-V guided antitank missiles were also capable of engaging enemy helicopters, and at distances beyond the range of the Igla." It also states the use of the R-60M missile "....it was found that under normal climatic conditions for central Europe, the R-60M missile could detect another helicopter or propeller-driven aircraft only up to a range of 2,000 feet."

@S.E.Bulba Thanks for the great pictures! :thumbup: :beer:

Thank you very much RagnarDa :beer: Yes, 3 months after my first report :P But joke aside, i don't care who reported what first. I'm glad RagnarDa found the problem and was able to fix it :thumbup:

Hi RagnarDa, i have no mods installed, clean DCS OB version(already tried repair), just putting the Viggen hot on the runway in the ME, nothing more is needed on my side. I thought the Radar must be running to trigger this crash because as i first reported this crash i could click many times my key bindings for the AP on my HOTAS(no double assignments) and it didn't crash but after a couple clicks with Radar running DCS stopped working. I tried it again today and it will also crash DCS without the Radar running, but it seems that you need more clicks to trigger it as back in march. Logs from today attached, i will also send you a PM with a private YT link showing everything from DCS menu to killing the DCS.exe. EDIT: Could narrow it down, activating/deactivating the AP ALTitude Hold mode 10 times(20 clicks - 10 ON and 10 OFF), on the 20th click DCS stopped responding. Another try showed that i could click over 20 times to activate/deactivate the AP ATTitude Hold mode without problem, after that my first click on the ALTitude Hold mode froze DCS. This time i used the mouse and the cockpit buttons to rule out HOTAS problems. dcs.log dcs_old.log

I tried it right now. Deleted fxo and metashaders2 folders. - restart and exit DCS -> new fxo and metashaders2 folders with files in fxo but empty metashaders2 folder - restart DCS and load a mission -> files in metashaders2 folder

Thanks for the info :thumbup: Thanks that Deka has implemented the DPlayer, so i just have to crank up the volume :smilewink: OT But sadly the Jeff has become my worst performing Module in VR(2D no problems with fps) of all modules i own....:cry: /OT

Bump This still happens to me in the latest OB. dcs.log

You are not alone: https://forums.eagle.ru/showthread.php?t=256850

It was in development by Belsimtek before they merged again with ED and the F4 got put on hold. Belsimtek1 Belsimtek2

Yeah, since a couple(?) patches it sounds like someone mixed a shower into the cockpit sounds.

I prefere the 2020 version tbh. You will not be able to get that 2017 look back because with one of the DCS 2.5(?) versions ED introduced deferred shading rendering to the engine and made it mandatory with the update to OB on 04-25-2018 https://forums.eagle.ru/showpost.php?p=3463558&postcount=8