St4rgun

For me right now is a hard stop after the AH-64D. I promised that no Multicore / Vulkan will mean no more buy for me. So with 20 modules and a TON of money already spent on VR headset and HOTAS in this GPU crysis I have to spare for a new GPU. It's much more important than a new module. If only we could get some info on DCS core progress then maybe I could revise my standpoint...

As I'm aware of no one said that anything from the dynamic weather will be inclued in the patch tomorrow... They said in the newsletter, that "We will soon roll out several enhancements for wider testing". 1. What is soon? 2. What is wider testing? Not sure that it means OB. So I think that's a tease at maximum, but no luck tomorrow for neither dynamic weather, nor anything weather related, sorry.

As I wrote previously the OpenXR WMR headsets (G2) can use the OpenXR Toolkit's inbuilt shaking reduction to smooth out the jitter of the IHADSS perfectly. And this is not only IHADSS related, it also helps a LOT in general to stabilize the view. All other modules with HMDs (A-10C II, F-16, F/A-18) are night and day when this shaking reduction is switched on.

in SP mode when perparing for landing at he last phase after getting landing permission from the ATC and successfully hiding the communication menu, then during the descend when I reach the GCAS set alert altitude and the "Altitude, altitude'!" tone sounds the radio comm menu pops up automatically and I have to hide it all the time with the proper hotas MIC switch button press. Very annoying. At DCS settings easy communicaiton is set to OFF.

If the clock, UHF repeater and the UHF radio frequency display are simple inverted backlit LCDs then it's okay, but in that case ED should model the LCDs visibility behaviour to enviromental light which would be tricky (clear contrast at daylight without any backlight which fades as lights are dimmer when it needs backlight to be correctly seen). Tha clock amber like colour on Snoopy's video then caused by the covering plexiglass before the LCD, so it's that amber colour without any backlight? I can't recall a plane in DCS which applies LCD screens without backlight and correctly modelled the screen behaviour, so this bug could need a serious work to solve...

So as trial license is trial license. As soon as I'll be able to try it for two weeks, I'll decide to buy it or not. Not before. Now I'm waiting for the trial license to show up.

All right, let's clarify: I listed all the instrument lighting which are supposed to work with Flight instrument dial but they are not working this way right now. Obviously what is working well is not listed. For me the Signal Lights Switch does not seems to work either. We'd like to have a clarification about the intended behaviour of these two light controls to be able to decide that the current status is faulty or not. One thing is for sure: right now at night in VR I can set everything to have a comfortable dim lighting except these: AOA indexer, clock, UHF repeater, UHF radio frequency display, NMSP buttons, signal lights.

So let's sum up. The Flight Instruments Lights Dial should control the following instruments in such a way, that in OFF state they should have FULL brightness for daylight use, and changed according to the dial otherwise: Digital clock UHF repeater UHF radio frequency display on the left console (?) Navigation mode select switches AOA indexer lights The Signal Lights Switch also should correctly dim ALL the warning and caution advisory lights. None of this dial nor the switch work as intended right now. Is that correct?

This is not needed anymore for them, because in the last OB patch they fixed the DSP rocker function for each MFCDs which can now control the backlight of the displays perfectly.

If those are controlled by the flight instruments dial then it means we should use that dial to full brightness in daytime? Which implicates also the throttle pinky switch to back for the lighting panel to function?

This solution is perfect for set up a night mission, but those settings are too faint for daylight. In that case one should change the settings based on time of day which is a hassle. @Snoopy, in the real jet are these things (UHF radio main display, radio repeater and digital clock) have fixed brightness, change brightness automatically, or connected to one of the instruments lighting knobs? Thanks.

+1 The clock and UHF radio indicator on the front panel is way too bright even at dusk. If this is a bug (like those should be able to controlled also by the Flight instrument lights dial) then this would be the good time to correct this also. As I read the team was working on the MFD brightness as well right now.

Try out the -50% or even -70% reducion. All the symbology will be silky smooth and stable in air.

It's a pity that Meta's headsets lagging behind on this field. On the Reverb G2 it is obvious that the small jitter is caused by the very fine movements (pulse mainly), but it's aggregated by the IHADSS implementation of ED as we discussed before. I hope that ED can think about some standardized solution, as @BIGNEWY also uses Reverb G2, so he can try out the existing shaking reduction of OpenXR Toolkit to convince the team about the feasibility and usefulness of the filtering.

Fuggzy, if you are using WMR with OpenXR then you"re lucky too. Check out my previous post about OpenXR Toolkit's shaking reduction feature, it's a blessing. It really makes wonders. If using Oculus or Varjo then I can't help, maybe someone have a solution for those users too.

Dear @BIGNEWY, sorry to disturb. You mentioned that it's possible to forward the ideas to the team. Based on my previous reply at least the WMR headsets CAN apply stabilization right now when using OpenXR. Based on that it's worth checking the existing solutions on other VR platforms as well, but it can still provide a proof that the HMD movement stabilization is not only usable, but MANDATORY for DCS. If all platforms already have proper solution then it's great, it will not need any further development.

To say some news for this topic: I've just tried the "Inputs" option of OpenXR Toolkit (I'm using Reverb G2 with OpenXR). There's an option which was pretty much under my radar before: "Shaking reduction". OMG, what a difference! I set it to -70% and EVERYTHING went smooth, without any annoying lag. I mean REALLY smooth. Not only the crosshairs will be so much better, but the whole scene inside and outside the cockpit. WOW, it's a jaw dropping moment for me. I highly urge all WMR usees who're using OpenXR to try this out, it's a really game changer.

I tried to check the fine details of the LMC function of the TADS optics as a CP/G in stationary hover and noticed, that if I switch to high zoom level and set a really slow crosshair speed with the LMC to track a target far away and then switch to wide angle optics then the speed of the crosshair becomes much slower. This is normal, I suppose the speed is angular speed which SHOULD remain constant without any joystick correction to be able to switch safely zoom levels without losing track. However when I switch BACK to high zoom level I noticed that the movement of the crosshair became faster, like the angular speed rate is increased without touching on the thumbforce controller. When I switch back and forth between the high zoom and wide angle several times it will end up a very fast movement of the crosshair. If this is normal in the real Apache then all right, but I suppose this is not the case.

Ohh, as I said in the first sentence: "Is it me..." Thanks, the CB AM radio indeed works. Bad transmit button press, ehh. Thanks. As long as I can give orders to the wingman it's much more safe to let him land first.

Is it me, or something odd is going on generally with the A-10C II Nevada CAS instant mission: the wingman reports targets of opportunity at the beginning of the mission, yet he's not answering to FM radio calls. I can't give any orders to him I double checked the FM frequency in the mission editor: it's 251 MHz, so tried to use that frequency in man mode and preset channel 1 also, with no luck after successfully completing the mission on my own with an unusable wingmen circling around we made RTB along the planned route and I manage to land correctly just to struck in the back moments after touchdown by my own wingman Somehow the AI understands that we're about to land (based on speed, landing gear and flaps status). Yet he's moving erratically (jumping up/down in the air) or worse - as I wrote previously - is completely out of sight (behind me) just to be in the worst place the worst time seconds later. Ain't the the AI somehow sense that I'm in front of him on the runway and acts accordingly? This way this SP mission is no joy...

I'm really into a fine A-10C II campaign, I'll definitely check this out. But only if the A-10C II FLIR is usable. Last time I checked this out some days ago on the Caucasus map the FLIR image was pretty useless to point infantry. Right now the instant action missions are all unusable because of this. Is there a change on this field?

It was an obvious typo by SilverDragon which I automatically corrected here. That discussion was about Vulkan API. You are right Vulkan deployment was not announced to be in the near term, the last "announcement" was in the 2021. January newsletter which "announced" it for Q3 2021. as a "planned date". I know, I know it is not "set in stone" blah, blah, blah. Since then they chose it's better to not "announce" anything just to be sure. The standard "development is ongoing", or "making good progress" are the only info. The one and only "Multicore Development Report" on Oct 15th 2021. was the last "detailed" info on that topic. Based on that I assumed that at least half a year, but realistically a year more is needed which would mean Q4 2022. But now I say this could be 1-3 years, who knows? I honestly understand everything, it's normal that they didn't give regular infos in the first 4 years on the development. But after passing some "announced" "preliminary date" I think the community is deserved - not the deployment, but - at least info on the progress somehow regularly. I don't ask for impossible things, just some report at least quarterly or to be more generous once per half a year. After the last such "detailed" report more than half a year is passed. If in this (hopefully) last phase of the development a developer can't say a word about the current status at least twice a year then it's really depressing. I simply lost interest now.

As SilverDragon wrote in the Roadmap topic: "No Vulkan near term release yet.". What is "near term" for ED if we are talking about complete graphic engine rewrite? A month / quarter / half a year / year / decade?

Let's partly open this issue up again: if I switch to external view (F2) then back to the cockpit then the blue cursor shows up, like I was moving the mouse. It will disappear quickly, but it's still a bug. The cursor should show up only upon mouse movement.

SkateZilla, thanks for the very detailed explanation. In my dreams such a detailed list is converted to some GANTT chart by ED and making some kind of progress % on each items. If that comes alive we'll wait for years while watching the progress to grow. The people here losing patience because of the lack of progress indication. But I already wrote this 100 times.