rubbra

I know this is resurrecting an old thread, but has anyone encountered SimFFB (incl the version linked a couple of posts above) randomly causing *extreme* violent shaking of the FFB device (Sidewinder 2 + extra resistors in my case) ? It'll typically do it on startup for me.

Why is there a plan to implement right hand traffic in Cyprus? Has it changed really recently? I'm pretty sure it's left hand traffic... (e.g. https://www.cyprusparadise.com/articles/practical-information/ and https://www.enjoytravel.com/en/travel-news/driving/driving-in-cyprus-15-things-you-need-to-know and https://www.worldstandards.eu/cars/list-of-left-driving-countries/ ) edit - I see the description has now changed to say left hand traffic.

Parking brake on. That’s all you need. (And no rearming or control input to move the aircraft)

Amazing, thank you!

Last night I was flying WSO with a friend. Ticking along at a solid 40fps in VR (locked/ASW). He turned on the A-G radar, frames dropped a bit. Turned on HRM, I get black screen/hour glass for a good couple of minutes, Oculus complaining that a hardware error had occurred, couldn’t track my movements etc, until he changed the MPD away from the radar; even switching modes to GMT didn’t help. As soon as the radar was off his MPD, back at 40fps. Now I’m not on an amazing CPU - i5-8400 - but I am amazed that the front seat turning on the radar would make my session stop. I get a bit of stutter in single player when I turn the radar on, but MP appears to be a “just say no” for the A-G radar for me. Any tweaking tips?

Annoyingly I didn't get a screenshot, but I just ejected (as WSO) over Syria, then started to have a walk around on the ground. My WSO's shadow had no head, from any angle.

I am not 100% sure, but based on a limited amount of testing, I believe that clients joining a server with F15Es on it require more RAM than those without F15s. e.g. tonight I joined Grayflag Syria with 31 players on, Windows killed DCS because it was using too much RAM. I profiled it, and got to 36Gb of memory allocated just at the Slot screen for Grayflag, after a reboot. I then joined another server with no F15 slots/players, 27 people on it, Syria, also after a reboot, 26Gb of memory allocated, a whopping 10Gb less. I've done similar with Sinai maps and found very similar numbers. The obvious test would be to make a server running a mission with an F15 slot and something else, e.g F16 and have two people join, measure RAM usage. Then repeat without the F15. But as I don't own the F15 and don't fly with anyone that does, that's a hard test for me. MT, VR, Rift S, 32Gb RAM, 1080ti. Never had DCS be killed for using too much RAM before. Grayflag Syria on the last release was using about 24-28Gb for me - I happen to know because I was testing the impact of visibility vs textures.

I'm on a lowly Rift S, 1080ti, i5 8th gen, and it's the best performing map by far, with the odd stutter here and there low over cities, but I get that on every map. The growing tree thing mentioned above is to do with visibility distance; the higher you have that, the further out the trees grow. Applies to all maps. Edit: wanted to make it clear that Caucasus suffers from the same inflatable trees issues, it’s not just ugra maps.

Can reproduce at Ramon too (F16 Instant Action Cold Start), but not all trees; palm trees seem immune.

Behaviour - in VR, tops of trees rotate with your head. Reproduce: In VR, Go to Instant Action, F18, Free Flight. Look to your left, move your head left and right. The tops of the trees rotate. I have tried to capture a video, but this behaviour doesn't show in the 2d desktop VR mirror. MT version, OpenXR, Rift S.

You can use the old version with MT, you just have to create a link - it's covered a couple of pages back. Basically rename the bin\dcs.exe to something e.g. bin\dcs.st.exe, then use mklink to link bin-mt\dcs.exe to bin\dcs.exe

In Vr by any chance? I have also noticed a huge performance difference of BS3 vs pretty much anything else. I’ve been flying quite a lot of BS2 in 2.8 recently, constant 40fps (ASW locked), in all scenarios, including the last thing I did before the update came out, which was the Caucasus instant action shooting range. Do the same with 2.8.1 and BS3, and I’m struggling around 14/15 fps. I had assumed it was just BS3, so gave up on it in disgust assuming it will improve in later releases. I hadn’t considered it might be BS2 as well - will test tonight.

I’ve recently found that Openxr toolkit (or perhaps opencomposite - the combo certainly) causes that behaviour on all modules and also constant micro stuttering in MSFS and il2. I’ve disabled it for now

Not entirely related to boresighting, but still IHADSS + VR... Do any other VR users experience the IHADSS not quite being central (which I guess might be true to life?), and thus having to choose whether to have ALT or IAS in focus? On my Rift S, with default VR "IPD" in DCS, the Altitude is always slightly out of the "properly rendered" circle of sharpness. I can fix it by setting DCS' IPD to 75 or higher, but that's not ideal, or by shifting my HMD off centre, which is uncomfortable.

I will endeavour to add screenshots to this later.

(I hope this hasn’t appeared already - couldn’t see it!) Problem: George’s target list is hard to see Oculus Rift S, using Oculus runtime (i.e. not SteamVR), just in case that makes a difference. Monocle set to right eye/default. George interface appears fairly high in my FoV - would prefer it a bit lower, I think, but not a big deal - which is fine, nice and visible. Tell him to slave to what I’m looking at, and then he produces a target list. Which is nigh on impossible to spot/see as it overlays (mostly) the bottom left of my view, often over the dark cockpit instruments. Sometimes it appears on the right. Not sure why. Also, I see that list double, unless I shut an eye. Workable, but probably not the optimal solution for future releases.

Yes, sorry, I spotted that you’d said this as soon as I posted, hence my post was deleted

Really? I’m on a 1060 and I have no problems with it at all. VR performance in the Apache is better than the F16 for me (which is the 2nd worst performing module in VR for me, Mosquito is worst). I get solid performance from it in MP and SP, probably about the same as I do from the Ka50 in the same circumstances.

*some* people will find that. some will not. I went from zero to many hours with no problems at all. And others get sick instantly. To the OP - VR. Always VR. It’s amazing, as long as you can get your head around the fact that you will be very very very unlikely to get the performance and image quality you currently get in 2D, and then spend ages trying to tweak your setup to get that perfect balance. And then find it, just as a new release comes out and the performance game changes, so you have to start tweaking again. But… it’s totally worth it.

Hah, I know what you mean! I posted on discord yesterday asking for help to work out what I was doing wrong - new to Harrier - and felt like it was a me thing, but couldn’t work out what it was. The patient folk on said discord told me their process, I wrote it down, went through it on active pause to make sure I wasn’t being daft, no luck, re-read Chuck’s guide, same thing. Then found this page. Made me feel a lot less useless!

I *believe* I’m seeing the same thing, though have also found that SSS to INS will allow me to launch (so no need to cage/uncage). I don’t have a track but do have a youtube video showing the behaviour. (And can easily make a track if it would help - it’s 100% reproducible for me) I thought I was going mad… The youtube video description documents the process I was trying to follow, but essentially, I find target, uncage Mav (in range), cage collapses so lock achieved, SSS fwd to set IRMV as SOI, try to launch, Beep, launch fail, try a few more times, then press SSS fwd again (INS == SOI), launch.

Has anyone else found that this mod is mostly not needed in the latest update? I've got significant fps gains, particularly in the Hornet and 'Hog. Viper is still worse, but still a good 10-12 fps higher than previously. I can only put it down to the "Fixed a bug leading to a drop of performance when rendering a water surface" line in the changelog - I fly a lot of persian gulf...

Well, if you’re not flying in VR (which I’m guessing you’re not if you’re on a 48”), I’d click on the High preset and start there.

Try windows-y and see if that enables the mouse? Sent from my iPhone using Tapatalk

I wonder if it might be helpful to start a new thread for this now, as there seem to be several "variants" of this patch around, and getting a consistent and useful story about how to apply them all is quite hard from this thread.