cloudkake

Sorry to bump this but i had the same problem someone else did, mapping the fuel flow lever to an axis unfortunately causes this not to work. Mapped it to buttons instead and now autohover is working perfectly. Maybe the axis endpoint can be tuned.. ill mess with it and report back.

ok i can manage that lol. Thank you, on behalf of the lazy people

ahhh ok can anyone point me to a good tutorial for the ALCM alignment? Ill check out chucks guide too.. Thanks guys

I always used pre-aligned mode. I can see it says "fast alignment' in the special menu now, does that mean this has changed? (sorry im lazy!)

Hi Guys, in 2.7 i start up as normal and when switching to NAV on the INS i now get nothing but the compass at the top of the HUD. Has something changed or am i missing something really stupid? All warning lights out etc.. Has something changed in its preflight config since the 2.7 update im missing? Thanks.

just thought i'd bump this a whole 4 and a half years later. I'm amazed this awesome feature was just left unfinished like this... Have Razbam just given up on this function? EDIT: is this finally it coming in the 2.7 update? Improved: Synthetic Runway created from ILS data and CP/PD info instead of mission editor

Yes i have these bugs too, I also notice the Flight director has many bugs multicrew rear seat, glide slope doesnt work either in the rear when working in the front. I do many lessons in this aircraft, i think its the PERFECT trainer! I really hope the instructor seat multicrew bugs get sorted out because its such a great aircraft to teach in.

Hi guys, Has anyone encoutered issues with the navigational equaipment from the rear seat? I've flown a few times in multicrew where only parts of the flight director seem to work in the back seat if selected from the front seat. For instance, when the front seat brings in VL mode on a chosen Tacan that works fine and is visible from the rear seat also. However, if altitude hold is selected that doesnt show in the back seat. The same problem exists when using the ILS. Glide slope will not appear for the rear seat. I've also noticed a bug where not all of the digits on the rear seat VOR/ILS radio pannel will show. DME will often not show in the rear seat where it will in the front. If i run the same mission as single crew so i can freely switch between the front and back seat then everything works fine. It just seems to be a problem with multicrew. In the case of wanting to use the IFR Hood (rear seat mounted), where the instructor sits in the front seat and student in the rear this becomes a real problem. Anyone have any ideas on this? I could grab some screenshots if that helps? Thanks.

That my good sir did the trick! ILS turned on with the wind at 6 knot headwind. Good to know this, thanks for posting

Vibora, thanks for confirming, i appreciate it. DrPhilbes, That could very well be the issue indeed! Thanks for letting me know i will do that and see what the result is! Many Thanks

ill check with another plane, good idea. Yes these are active ILS. Tested with 0 wind or weather that might cause issues.

Hi Chaps, Im having real trouble getting the ILS to pick up in Syria, especially the northern most airports where the frequencies just arent picking up at 3000ft on a 10mile final, on radial where they should. Is this a bug? The VOR with DME is working fine but switching over to any of the ILS frequencies appears to be fruitless. Only in Syria im getting this.. Any advice appreciated!

precisely my thoughts. Ah well, we can work around it.

We all know that ground crew like a prank. Harrier-glue will always be funny to them.

if you need more travel than 82 degrees in a hover your hovering is very out of shape But yes i take your point, if thats the correct mechanical operation of the stop then so beit, i shall work around it.

remove before start up

I wouldnt mind if you could VTOL out of the chocks but sadly they come with harrier-glue

First off, love the new updates to the Av8, top work on the pilot in VR looks incredible! One small thing i do wish was considered however; the Nozzle Stop! I dont have a problem with the 5 degree increments when working on a joystick axis, but i now can't set 82 degrees on the stop! This is the perfect position for hovering and between 75 and 99 degrees is now not adjustable on that axis Does anyone else use this or just me? I use one side of the throttle to act as the Nozzle axis anyway but it was great coming to a hover having that 82 degree stop so i didnt have to think about that.

I never knew that! Very good to know.. however no numpad on my keyboard? Any other way around that? EDIT: scratch that, you can do it from the oculus debug tool. For some reason last version it wouldnt let me but latest update it does. Also re ASW, if you're not hitting at or above the refresh rate of the oculus, beit 72,80 or 90 then it will lock 50% of that framerate as its designed to. With it off you will obsiouly see a higher frame rate than the locked 50%. You're still pushing what you were before its just doing its thing to keep it smooth when youre not at or above native refresh. However, some prefer it off so as long as its not giving you any motion sickness and the perception is smooth, there is no harm in trying it out! As im about to

Hi Guys, Small issue i cant figure out here using thr AWLS system for landing. I cant work out why but the distance to the runway is displayed in the HUD as a huge figure, something like 52030.12. when i see footage from others i either see TCN with the distance in NM to the runway or DME with the same NM number as is reflected from the left MPCD in the top left corner. I can just glance down at that for my distance to runway but ideally i dont want to take my eyes off the HUD in IMC on final.. any ideas? I also noticed when using the course line on the TACAN that it will only work on the most zoomed out map layer on the MPCD. It would be nice to zoom in and still see it. Is that a bug? Thanks in advance!

you're doing everything right, the flashing seems a little concerning. Have you tried another USB cable or another USB port on your computer? Also have you done the Bitrate test on the cable? RE the 1.7 i went to have another glance, and yes the max output res is to native quest res at all hz settings, it just says 1.7 at the top of the slider on 90hz instead of 1.5 at 72hz and 1.6 at 80hz though im not sure of what this slider is referring to exactly.. i need to do a little more digging as its doing something different to what the debug tool does of which i was previously used to.

Yes, surprisingly this was something i verified with a few other quest 2 owners quite quiclky. According to Carmack, the 1.5 res of 5048x2736 is not a random number plucked out the air but the actual native pixel density of the Q2. So as much as its referred to as SS its actually not to this point. To go into SS you need to run 90hz and then up to 1.7 will be available and takes you into SS teritory. In either case running at native res with a given hz seems to provide a really nice smooth experience where the lower res doesnt (oddly) for me on a 1080ti and i can easily read everything in the cockpit now, i can hit the sold rear projection figure all the time and maybe a third of the time out of it, so happy days. All we need now is for ED to do do their bit to help us VR users out with some optimisations... but ya know...years have passed. Also if you're after comfot improvement, i printed this from thingiverse and it made a huge difference moving the weight to your forehead instead of your face. Basically converting the headstrap into a 'halo' type instead. Find a friend with a printer if you dont have one! ;) ​

Well i wish i'd seen this thread before buying! Ah well, it does fly nicely and for me in VR its a pleasant experience up front. However, multicrew in VR, wow there is sooooo much broken. I had to despawn and jump back in to see the engine running from my friend flying it in the front. That carried forward to most changes made by the pilot. ie gear up would work fine up front but from the back seat just stayed down, both canopies stayed open etc etc. Whilst im fine with early access, this is outright broken and obviously going to get more broken as DCS rolls forward. I would've thought there was a minimum benchmark for ED on this to take peoples money, this does feel below that even as someone very forgiving of these things. Certainly makes me hesitant knowing this can happen. I felt a little stung when the hawk left, still hurts actually haha! Anyway, long short, if you VR and want to multicrew, 100% avoid, its soul-destroyingly broken there.

Its pretty easy to sideload the latest update, youtube search it. Takes about 5 min of your time.

good work dude, will bookmark this page. Perhaps one for quest 2? few things are specific to that pannels res when using the oculus debug tool etc.