unknown

You can ramp up the pixel density, you will have a crystal clear high resolution picture but DCS and the HW is not capable to render that in a satisfying fashion - render time will be seconds per frame instead of frames per second

+1 for that.

.ogg is also supported - setup is the same if you use .ogg instead of.wav - wave = "/Effects/Cockpit/DPlayer/music_xx" not ogg=....

I also remember that quote, but if i remember correctly they never said explicit if this is also true for VR - atleast i hope so.

Yeah, stable and beta have the same version right now -> MP compatible everytime this happens.

Thats also what ED aims at atm, from the patch status thread: "Next update: Planned 31st March 2021 ( subject to change )".

Ah that was a joke, yes i missed that totally...must be because of little free time...thank you for clarifiaction.

EDIT: Just ignore my post, i was misinterpreting yours.

Nice to see some news about the Hind! Somehow i didn't received the newsletter for two weeks, i had to resubscribe after years without issues- strange

Ok i had some time this morning to watch your track. I think the track is not replaying correct(?) because you crash in a dive after 3min. But that is no problem, i renamed the .trk in .miz and flew it myself to test the mission. Short answer: - the enemy is close and flying slightly above your radar cone/covered airspace. Long answer: - in the video you posted there was the problem with the radar elevation moving to the max down position - this is not the case anymore in your track - to be able to use the BVR(TWS) "mode" in that mission you have to bind the radar elevation axis and you need to work it - make sure it will not jump to positions you don't want like in the video you posted - if you move the radar elevation slightly above(up) the default/middle position you will start to see the contacts on your radar - they are close(less then the 40nm default radar range) and flying slightly above the radar cone in the default position ~1k ft - additionally the JF-17 is slightly "limited" in the radar cone coverage - depending of the radar mode/scan azimuth your scan bars(elevation) is more limited than in other jets(F-18...) - you can see in the picture/screenshot of the radar - enemy distance ~5nm and the hight coverage of the radar is only from 21k ft to 23k ft - right of the radar cursor - this is with a slightly elevated radar cone, in the default position(like in your track) it would only cover 20k ft to 22k ft at that distance -> no contact on display - for contacts that close you do the right thing to switch to ACM modes sorry for the crap drawing, but i had not much time

I'm a little short of time right now, but i downloaded the track and will have a look as soon possible - that could be today or in one week - i don't know right now...

A track would be great! A quick test on my side with B-52's and F-5's showed no problems on my side:

They already said that the implementation will come in several stages. From the January 8th newsletter: "The wait is almost over, and the new clouds for DCS World will be introduced in the 1st quarter of 2021. In addition to being visually stunning, the new clouds will block visual and optical sensor line of sight and be synchronized online. We will initially release the new cloud system with an array of weather presets that will cater to most mission building scenarios. Later in the year, we will update the Weather Tool in the Mission Editor that will allow finer control of the clouds with a dynamic weather system based on a more advanced meteorological engine."

If you want "static" aircraft with weapon loadouts you could place the plane as AI(before you change to player/client) instead of static, select your loadout AND set the FUEL to ZERO, with that little workaround you ensure that the AI is unable to do its start/takeoff/land routine. I don't know if the AI will start if you set internal fuel to zero but attach external fuel tanks as part of the loadout.

Sadly the resolution of the video is not very good, i can't read anything(settings) on the displays. Is that your own mission? SP/MP? Could you please post the track - just start the mission, test the radar to show the problem, hit esc, in the result screen there is a button called save track, upload it here. things i noticed: - you said you removed the antenna elevation mapping but as the video starts your radar elevation is centred(good) - a couple seconds past in the video and your radar elevation was set to down(-60°), so there is still something assigned to the antenna elevation axis???(bad) - as you switched to TWS? the antenna elevation axis looked like it was centred again, will check later if there is something fishy? A track from you would really help here! - after your acm engagement as you switched back to "bvr" you saw the track real close and disapear at ~1.57 in the video, that was probably because it left your radar scan cone - here you would need to change the radar elevation so that the target stays in the radar cone - you can check whick elevation area your radar scans at what distance with the two numbers right of the radar cursor - lower and upper limit

You have to set them as client not as player. With the client setting you can choose on mission start what plane you want to use or while the mission is running you can hit esc and select another plane. If you have planes in different coalitions you will be prompted with the coalition selection before the plane slots.

I tried to find the comment from one of the Deka devs but failed to find it. I'm sure there is a limited number of times you can connect/select a missile in flight, i just can't remember why that was.... Maybe @uboats @L0op8ack can clarify?

You can get that already with the JF-17 from Deka - WIP. And no - it's not the over wing vapors, that effect looks different. It also has: - canopy fogging - you have to connect G-suit and Oxy-mask connectors on a cold start (should be 1440p after YT processing)

The only other thing that comes to my mind beside what Mustang25 said is that you have mapped the Antenna elevation function to an axis(double assignment?) that puts your radar antenna to the lowerst/highest position preventing you to see any contacts. But this is all just guessing, post a short track or video/screenshots. The radar works fine for me.

According to google translation(russian-english): Can you please fix the crooked wheel The plane hangs above the surface

Yes, sadly.

Thanks for the clarification!

Nice that i found this thread, i thought i have missed something because my AIM-7M just gone stupid after launch. So i tested agains a Su-24 and can confirm: - me in F-14B shooting AIM-7M(Jester STT lock, never loosing it) at Su-24 -> my AIM-7M goes stupid as soon as it leaves the rail - me in F-14B shooting AIM-7M(Jester STT lock, never loosing it) at Su-24 with ECM = off(advanced waypoint actions) -> my AIM-7M lofts, tracks and kills the Su-24 - me replacing the F-14B with the F/A-18 shooting AIM-7M at Su-24 -> my AIM-7M lofts, tracks and kills the Su-24 without the need to turn ECM = off in the advanced waypoint actions So why does the AIM-7M work against jamming targets in the F-18 but the same missile does not work against the same target fired from an F-14B??? What is the difference? What am i missing? F14B_AIM7M_SU24_ECM_OFF.trk F14B_AIM7M_SU24_ECM_ON.trk F18_AIM7M_SU24_ECM_ON.trk

I'm no Mig-21 expert, it's been a while since i read the manuals, but from what i remember the fuel pumps are "just" used to manage correct fuel flow from the tanks to the engine in situations gravity is not enough. From the Mig-21bis flight operations instruction, you turn on the fuel pumps after engine start:

I thought that it works like the current static weather templetes in the ME, you just select one of your liking - summer, hot, clear sky / autumn, rain storm....