Hippo

I've been running on my probably not very capable (i.e. cheap) Philips HDR 4k TV. When I flick the HDR "slider" in the W10 display settings, it just switches off again. Does anyone know why this might be? A few weeks ago, I had somehow got HDR to "work" in Doom Eternal, but it looked awful - very washed out. I also experienced other issues, such as the signal cutting out. A firmware upgrade for the TV did a lot to improve things, but I suspect the TV firmware might still need more work. I've been very impressed by some material I've streamed from YouTube, but underwhelmed by a lot of other stuff (e.g. Jack Ryan on Prime).

Agreed. 4k, 8700k w/ 1080Ti, 16 GB. I'm using HIGH w/ rendering at 80%. Looks great, and can get just over 40fps in most places I've tried. 99% of my testing has been with the smaller aircraft. (i.e. no airliners) I think the OP might be referring to running at ULTRA where the scenery is particularly demanding (e.g. NY). Airliners perhaps. I watched the following the other day In my case all (12) logical cores ARE used. Core 12 sees the heaviest usage, with all others around 30%. GPU @ 99-100%. Constantly.

Actually, what you seem to have done, is to have read way too much into it. Have a nice day.

I have now tried doing this, and agree with you that the displayed fps incorrectly shoots up. I have no requirement to pop out windows, so had not tried this previously. I stand by my original statement, which if read precisely, refers to my specific, and limited experimentation. It is not my intention to get into arguments with anyone, I was just describing my own experience. https://ibb.co/5Y9ctpj https://ibb.co/hYkyX1R https://ibb.co/S34DM6R

Two things: 1. Re-read my post. 2. Get over yourself.

Is this a serious comment? All of the effects can be similarly simulated by moving the outside world. Whilst the cockpit shaking about is a neat effect, the game of "chase the tiny knob with the mouse around the instrument panel, whilst simultaneously trying to look out of the window" is not fun. Let alone for Track IR users. It'll be a nightmare in VR. I'd be amazed if the option to disable it is not added at some point. Why do some people who like the feature find it necessary to waste their time and everyone else's posting their "I like it, you're so stupid, and don't appreciate the realism" outrage here. No one's asking to remove the feature, just for the option to do so. 'Is this what humans call "trolling"?' as Kryten might've asked. As the OP, all I asked was "is there any way to turn it off?". Thanks to everyone who responded constructively.

Some people, and I include myself, find it just as enjoyable, sometimes even more so, to tweak settings and squeeze out that last sliver of fps vs visual quality. I.e. looking inside the cowling can be just as fun as looking out of the window. Beware, it can become quite addictive, in an OCD sort of way ;).

I'm also running at 4k. i7-8700k w/ 1080Ti (11GB VRAM), 16GB system ram. I am still tweaking, but using high, and then changing the scaling to 80% as mentioned above. I'm getting just over 40 fps outside of cities, probably losing around 10 - 25 fps in cities. Even though not on ultra, I still think it looks fantastic. Because I'm testing, I have v-sync off, but will turn it on for normal use. For this sim, on my TV, without headtracking, I think 20 - 30 fps is perfectly acceptable. Every single logical core (all 12) is being used, and CPU util looks nicely balanced. Avg is around 50%. GPU is at a constant 99-100%, and I keep thinking "do I smell something burning?". I've been ignoring taking my system to 32GB for ages, and will be doing so soon. I have a Reverb G2 on order, and am wondering what "compromises" will be required to get this puppy running acceptably in VR. I sold my Rift S recently, and had been exclusively VR for ages. Going back to pancake, and having to bind view controls to my joystick hat is taking me back... But she sure is pretty.

I've been using MSI Afterburner to benchmark, and I've seen nothing to make think that the readings I'm getting aren't accurate.

Depends on the aircraft. On the 152, the parking brake "knob" just holds the main brakes in place after activating them with the toe brakes. To release it's usually necessary to depress the toe brakes a teensy bit further, and then release the "knob". I suspect this is what the OP is referring to. AFAICT this is not modelled in-sim, and the parking brake knob and toe brakes are independent of each other. https://maintenancecessna152.blogspot.com/2012/09/parking-brake-system.html In the real 152, the parking brake is not the best. I would certainly never want to rely on it and always used the toe brakes when holding, etc.

Are you using a profile loaded in the Logitech software? If I set mine to "Clear" (right-click icon on notification area), then assigning custom views (I only tried custom view 0) works without issue. I do use a custom profile which sends the keystroke alt-0, this works for me. Also, you have saved the views first? ctl-alt-number. They are specific to each aircraft. In my profile, if I have the button set to "do nothing", then it doesn't work in the sim (assigned as joystick button). It does work if have it set as "unprogrammed".

Wash your mouth out with soap! But seriously, many thanks for the reply. It's nice to know that such an option is available. Really, I think MS/Asobo should offer the option to just turn this off. As for me, I've just bound the HDG change to my joystick. It'll do for now.

Please bear with me... To get my cockpit camera just as like it... I have changed the default zoom and height in the options (both to 65). This improves my view out, but doesn't let me see as much of the instruments as I'd like. So I've set up a custom view (alt 0) which is a slightly looking down variation of this default wide cockpit view. This is the just how I want it view, that I want to be my main view. So, I jump to it pressing alt-0. All good, and I'm one happy camper. However. I am also using the quickviews as required (ctl-arrow). When I release the quickview, I would expect to return to the custom view, but am instead returned to another view (which looks suspiciously like the ifr view). I can press alt-0 again (twice) to get back, but this is all too much of a palaver. Surely, when releasing the quick view, I should just return to my custom view. On the off-chance that someone else is trying to accomplish something similar, anyone else seeing this? And agree with me that it's wrong? Or I'm doing something wrong? If you've got this far, I thank you for your patience. It's not easy being me.

I've just bound keys to these and 45L gives me a 7:30 o'clock view, and 120L gives me a 10:30 view. I thought it should be the other way round. 45R/120R work as expected. Just checking whether anyone else is getting this.

As I use the mouse wheel to change AP HDG, it gets very old, very fast, that the knob "moves away from under the mouse cursor", and I change the view zoom. Arrgh!

I don't mean camera share (sorry if it's called something else, I don't have the sim open at the moment) in the options, which I have already turned off. But the effect where the whole cockpit jiggers about slightly (I presume to simulate turbulence). It can make it rather tricky to click on small buttons and turn knobs.

I should imagine that the developers well know that the community will produce websites, youtube videos, etc, so why should they devote expense to producing a detailed manual, when it can be focused on the sim. This seems reasonable to me. Having said that, I go into options (and I use this only as an example, I realise most will know what v-sync is), and select to turn on/off v-sync, what is the "description" on the RHS? V-sync: "enable or disable v-sync" Well, no sheet, Sherlock. That is not a description of v-sync, it is a description of a tick box. Would it really have been so much trouble to have described what v-sync is, for those who might not know? P.S. Before the rabid f4nboys descend on me, on first impressions I'm actually very impressed with what I've seen so far and an optimistic that we have a base on which much can be built over the next decade(s). But irritations like the above just grind my gears.

We seem to be going round in circles. Apologies if I have not explained myself. I understand everything you've written, so there's no need to just repeat it all again. However: At the very start of the installation, it gave me a list of DRIVES to choose from. I chose D and it did indeed install "the app" to D*, it did not default to C as you state. When I say a location of my choice, I mean I would like to specify e.g. D:\FS2020 and for the installer to put the app there. Specifying the drive and the having the installer create a number of hidden folders all over the shop, to which I don't even get read permission, is not my idea of "a location of my choice".

I've only really "tested" the C152, which I think is mostly done very well. It also looks great - for a default aircraft I think it's excellent. However, when applying full power for take off, the aircraft pulls to the left - HARD. No (real) 152 I've ever flown does this (to the same extent). I was using the "modern" FM. Is anyone really expecting detailed systems depth and realism from the default aircraft? For me, the true test will come when we get to see what 3rd parties can do.

Hopefully my posts describing my installation experience might help others who find themselves having similar issues. I'd definitely recommend having a full backup of your system before attempting the installation. It's certainly possible to pick the DRIVE (but not folder) you want to install to. You can specify the folders where the packages will go, as well as the caches. However it does create a number of other folders (WindowsApps, etc), some of which you do not even have permissions to access. On my first installation attempt it created these folders on drive D. On the second it created them on C. In both cases I requested installion to D, so somewhat puzzling.

Yes, I know all this. But, what's with the "let it install on the C drive?" - it gave me the option to install to C or D, so I chose D, why shouldn't I? The packages and cache can be put on D, and this is what I've done. The sim does, however, dump a number of other folders in several places over which you have no control (or access). I realise that this is "the way it is", but as someone who likes to have control over what goes where on my system, I find it irritating. Also, the installation failed on multiple occasions with no indication as to cause, it's nothing I did, it just failed. I have never had issues like this installing a flight sim in decades of doing so, this is not my first rodeo. Anyway, it's all installed and working now. First impressions are very good. I tried it out on my 4k 50" TV, and wow, this is a big step closer to photorealism - I am amazed at what they have achieved. Performance is surprisingly good.

Phew. The download completed, and I now have the game installed. Curiously, it hasn't created folders in drive D that it did on the previous attempt (even though I did request it). The Packages are on D where they should be, but I'm guessing the WindowsApps and other installation folders have gone to C this time. Inconsistent, and odd, behaviour, Ah well, time to try it out...

Stuck at 80% percent again. Closed and restarted. Press any key. Checking for updates. Blue bar. No indication what could be going on. I could now be stuck in a loop for ever. This is utterly woeful. But, no , ... Hello. Stopped and restared (again). On this attempt it is now downloading packages. just 91.36gb to go. Here goes nothing. Getting around 70 Mbps, which is where my connection tops out.

Why should I let it install on the C drive when I want it on the D drive, and I'm offered the D drive as an option?