Magnatilla

I'd recommend it if : You have VR You want to do some aerobatics In my experience, nothing touches the Yak for post stall behaviour, but it does have it's limits. There are some issues with the flight model around full throttle and high AoA, but you can work with them by flying within the limits from experimentation. It's probably not the best all round module, but I've seen nothing better for at, or beyond stall simulation, wish ED would fix the AoA bug though.

https://forums.eagle.ru/showpost.php?p=4216284&postcount=12 Also saw the threads on Oculus firmware update bricking your headset if you're on Win7. :(

Hi Don, my thoughts are that maybe the new runtimes for newer versions of Oculus (home) have a matching newer SDK/library linked when the DCS code is written/compiled. That's all I can think of as the headset is not detected in any way, even when forcing VR on the DCS command line, I would expect head tracking to work if the display is not enabled (from previous coding on Oculus stuff, admittedly a while ago). But nothing. hope that makes sense? I really do hope it's a bug but only ED can really let us know on this.

Thanks for chipping in fitness88, but I think what we're trying to establish from ED is if they have switched to only supporting the new API for Oculus. If they have switched to a new API, users like me are stuck at nothing newer than 2.5.5. (so no new modules that are not backward compatible to 2.5.5) :mad: If it's a bug we can look forward to enjoying the future of DCS when it's fixed. :thumbup:

+1000 I have a slow internet connection, downloading the latest patch each time only to find it won't pick up the CV1 and then rolling back is a bit of a labour of love. An official statement on this would mean I can wait to see if there's a fix or just not bother with 2.5.6 on wards.

For me the update for DCS was around 7Gb, but it can be resumed from a disconnection. Oculus for me downloads in sections and some of them are too big before I get disconnected. (ADSL internet here) I can at least carry on offline using 2.5.5, but as a user of the YAK, I bet it'll get the long awaited updates now I cant update! Sods law.... I'll hope it's not an API change and something will get fixed.

Sadly I don't have the bandwidth to successfully update Oculus to the new version, and it looks like DCS is now going to run using an updated API. So this probably spells the end of my DCS experience.....

Yeah, same here. No VR can be started for me. Bit of a disappointment. :mad:

Off the top of my head : Level of Detail - annoying for other online players if you turn up in a Yak. Inverted stall bug - really annoying if you fly aerobatics. Some synching issues for multicrew. Lack of ground effect? Engine model/failures. Have a look at the bug section if your interested :thumbup: https://forums.eagle.ru/forumdisplay.php?f=599 BN, i notice the inverted stall bug is not marked as reported, is there something needed?

yeah, i was confused by that too, still. this thread just keeps on giving....

Good to hear. :thumbup: Circuits and bumps, it's quite fun! And if you haven't got Natural Head Movement on, maybe try it as it helps you see which way the plane is starting to yaw before things get too far gone. I have more of a nightmare with the Spit myself. I-16 - If it hasn't started to swerve, you know it will so be ready. :juggle: Spit - May or may not swerve, seems that catches me out. :cry: I'll have to play with curves on it.

Looks like there's an unwanted curly close bracket before DcsBios::loop(); Change the last bit from // rebuild the picture after some delay //delay(50); } DcsBios::loop(); } to // rebuild the picture after some delay //delay(50); DcsBios::loop(); }

Guess you got no help from this thread in the end? https://forums.eagle.ru/showthread.php?t=241593 It is a challenge to be sure, but that's part of the charm of the I-16, I'd hate to see it changed, but the rudder help option could do with a few tweaks. Try no flaps, glide approach and be quick on the rudder, short inputs seem best, if the short input fails keep the rudder held on full. Curves help massively too, so I could take a look and suggest what I have when I get a chance. Otherwise it's practice. :joystick: Post a track, I could take a look and see if I have any suggestions if you want? :thumbup:

I've not used any of the hardware you're using to know for sure, but just from a standard C or C++ standpoint, you have no draw() function defined in your second bit of code. Does the one from your first code work if you add it? void draw(void) { // graphic commands to redraw the complete screen should be placed here u8g.setFont(u8g_font_5x7); //u8g.setFont(u8g_font_5x7); u8g.drawStr( 0, 22, "TEST"); u8g.drawStr( 0, 42, "NOw WORKING"); }

That looks so very broken..... :huh: I guess you've tried mapping the rudder to different keys, and maybe try a DCS_updater.exe repair?

Yep I get what you're saying, it's no biggie for me, just thought it might be relevant. I think you're maybe on the right lines with the stereo_mode_use_shared_parser = true bit as well, probably the clipping is only worked out for one eye but gets used for both?

Seems that way, I'm not at my machine currently but I can take a short video and post later if needed. Also I use a CV1 and it happens there too. I did see a Pimax video where the clouds disappear much more towards the center of the screen than the pylons do for me. It's most noticeable at high zoom, the race course tower pylon things disappear early on the left and bottom of the screen as the camera tracks a moving aircraft.

I also get this without using VR, especially when zoomed in a long way in external views. It just seems like the clipping frustum is not set correctly. I'm running at 1920x1200 res.

+1000 :thumbup: When I saw the patch notes mention fixing a memory leak, Record AVI was the first thing I tried and was happy to see it working again. A codec selector would be awesome.

Blimey, :surprise: That's surprising, is it really that bad on a 1080Ti too?? It's noticeable if I look for it with my 1060 in VR, I would have thought that card would handle it.

+1 I've only got a GTX1060 card and have been flying the Yak to an obsessive level :pilotfly: so on going back to other modules I've noticed the FPS hit with the Yak when there's a few others around. Hope this gets looked into as I don't want to be "that guy" in MP sessions who slows everyone else's FPS down. :cry:

so yeah, I'm slow... :doh: Exactly, and it's why I think we need to get a measurement from DCS. Am interested in the results you get and will try it myself when I can.

It's been a long hot Friday, forgive me if I'm being slow... bbrz, what's S.L. airports? I am guessing you're saying measure the landing roll, taking it as a relative distance compared to the runway length on map view? :helpsmilie: We await something from Moto but I'd assume he's landing as slow as possible from he OP: I'll put this out there too, does anyone else find the Yak to be very floaty with no engine landings, almost as if ground effect comes into play?

Ninja'd by Woodbuster. :thumbup: That was the plan, not sure how do-able it is but, hey, we could make a spot landing competition out of this.. {B-)

OK, so before we start fitting guns to our Yaks..... :huh: Moto, you might have already checked this but have you got a trk file we can see, maybe we can work out the stopping distance from that and compare? I've seen the stopping distance quoted as 200m for a Yak so can see your point. I have the brakes on a rotary control and for me the brakes are a bit nothing... nothing... face splatted on the instruments. :D Also I think there's a file where you can edit the friction coef. of the tyres, I'll need to do some searching..... :book: