-
Content Count
1,241 -
Donations
$0.00 -
Joined
-
Last visited
Content Type
Profiles
Forums
AVSIM
Media Demo
Downloads
Gallery
Blogs
Forms
Everything posted by Virtual-Chris
-
Maybe it's just me, but GAIST doesn't add enough ships to be realistic. With only GAIST running, I get maybe one ship. If I layer on the Seafront Simulations add-ons for both the sim-generated AI ships, and their own ships, I get several ships. Another problem with the oceans in general, is they are just way too calm. Real world oceans are not as calm and smooth as the glass we have in the sim. It's not immersive at all.
-
I like your view on things... you have no issues, but you have to hit a button twice after loading into the sim to get into the proper position because you're out of place. 😄 Anyway, I don't know why they don't just fix it. Hopefully it ends up being net better than Track IR, but as it stands, it's a pain.
-
Simbrief for ils approaches
Virtual-Chris replied to Hyper14's topic in Microsoft Flight Simulator (2020)
I'm not sure you should be planning an ILS approach as part of your flight plan anyway. I think the best way to fly IFR is to not have an approach in your flight plan, and wait for one to be assigned by ATC when you arrive. At least this is how it normally works in the real world... and in-game ATC supports this. Unfortunately, ATC in the sim can pick a random approach, and not necessarily one based on real-world weather or active runway usage, but at least you're going through the motions of entering and loading your approach on arrival. Then use Navigraph, ideally on an iPad or tablet or somehow in game, to consult the approach charts so you understand what you're about to do. If you add an approach to your flight plan, ATC will not change it, and you're missing out on that whole aspect of loading and activating your approach on arrival. -
It sounds like everyone's just accepted this bug 😛 You shouldn't need to press it twice... in fact, you shouldn't need to press it at all. Why does it have to mess with the starting head position at all? Track IR doesn't bugger with your head position when you load in to the sim! I say it's buggy and needs to be fixed.
-
Both systems have their pros and cons. I switched from Track IR because it seems to be dazzled by bright lights in the back of the room so was unusable for me in the late afternoon when sun was shining in the rear window of my room. So far, this isn't an issue with the Tobii but it's still early days. I've found both solutions are fussy with placement and setup. The Track IR cam being on top of the monitor can be an advantage in many setups. The Tobii has to be chest level and arms length away which can be challenging in a home cockpit with yokes, and stream decks, etc. Not having to wear anything with the Tobii is certainly liberating. The Track IR seems to offer more control over movement ratios as you have a left and right curve for each individual axis. But that added flexibility also makes the Track IR more complex to get setup just right. So far adjusting a couple of sliders on the Tobii has me in a good spot. If I can just sort out this starting head position issue. I'm not sure why it feels it needs to move my head position to some bizarre spot every time I start the sim. Why can't it just press F12 twice on its own at the start? Why do I need to do that? And why press it twice? There's something not working properly here, and it seems most people don't care as there's somewhat of a work-around. Bottom line is, neither of these products is all that... both need some work.
-
I recently setup Tobii to replace Track IR. However, every time I load in the sim (into the Kodiak) my view is either behind the seat head rest or inches from the glare shield. I ALWAYS have to use the keyboard to setup my view where it should be. I’ve tried saving my VFR cockpit view but that has no effect. Has anyone else struggled with this and figured out a solution?
-
Does the laptop display have G-Sync? That’s a key consideration for how you handle tearing. Frames jumping around between 60 and 120 is normal and actually word not allowed good! This sim is heavily constrained by the CPU in almost all cases except perhaps in a 152 in the middle of the ocean. 😝 And thus your FPS is a direct function of how much work the CPU has to do to create the scene… scenery, airports, photogrammetry, buildings, objects, AI traffic, etc, all have an effect on the CPU and thus your FPS at any given moment.
-
DLSS 2 vs.TAA vs. DLSS 3 + FG
Virtual-Chris replied to Fielder's topic in Microsoft Flight Simulator (2020)
There was recently a longish thread on ideal settings for Nvidia owners here… See my settings recommendations about midway down the first page. -
DLSS 2 vs.TAA vs. DLSS 3 + FG
Virtual-Chris replied to Fielder's topic in Microsoft Flight Simulator (2020)
Thanks. Can’t watch the video now but will tomorrow. I don’t feel a need to use DLSS scaling to get added performance. Just FG for me at 4K native is generally giving me fantastic FPS with a 7800x3D and 4090. It doesn’t sound like he tested it, but there’s a third choice for antialiasing… DLAA which uses Nvidia’s ML models and tensor cores to do anti-aliasing but without DLSS scaling. I really encourage every GA flyer to try DLAA vs TAA. It’s a quick and easy test. Find a windsock or antenna or other artificial small detail at the airport at some distance from your plane… and then try switching back and forth. I found thin details at a distance didn’t even render with TAA, but I had a bit of ghosting on my displays with DLAA. Updating my DLSS DLL sharpened up the cockpit without losing the details. Then I rebuilt my system and I was surprised that my cockpit is as sharp as ever with DLAA - no ghosting at all. I have no idea why, but I’m now using the DLSS DLL that came with the game (beta SU13) and it’s perfect. Fine details in the distance and sharp cockpit instruments. I dunno. Try for yourself. You might be amazed. -
Not sure, but you can get touch screen support using the Pop Out Manager utility.
-
I’m not sure that matters much. RTings tested it and the C1 is good for G-Sync below 20FPS. God forbid anyone has FPS that low 🙂 I have a C1 as my primary monitor (but I’m driving it with a 4090) and it’s been fantastic. Amazing color, contrast, and g-sync performance. A bigger issue with high refresh rate OLEDs is a bit of OLED flicker in dark (night flying) scenes at low FPS. It relates to the charge duration of OLED pixels. But if you can keep the FPS up this won’t be an issue… and if you have a 4xxx series card with frame gen, this certainly won’t be an issue.
-
Personally, I don’t like this kind of design… no ventilation out the top… you’re going to have two large fans pulling air in the front and two or three fans pulling air in from the bottom (GPU) and just one exhaust fan on the back?! It’s not ideal at all. You’re going to have to leave the side panel off for sure.
-
That all sounds good, but see my post (#2). I think 64GB of RAM is going to largely go unused. I never see MSFS go beyond high-teens. I opted for 32GB with faster timings… 6000 is the sweet spot on these platforms, but you can probably run this kit at 6000 with tighter timings. I also think a three fan AIO is overkill. I run an Arctic Freezer II 280 and temps are never an issue. But if you have the case for it, why not. I really don’t like tower cases as you’re typically forced to put your AIO rad on the top panel, which means you’re pushing air down into the case… I prefer my cases to work like a chimney… pulling cold air in from the sides and exhausting out the top. Hot air naturally wants to rise, and i try not to fight that. If you can mount your AIO on the front of a tower and exhaust out the top, great.
-
I can’t imagine why the rolling cache would be CPU specific… can anyone explain this? In theory, it’s going to save data downloads from the cloud… and that could be a game changer or non-factor depending on your latency to the MS servers… and shouldn’t depend on CPU choice at all. I run rolling cash as access to my SSD is orders of magnitude faster than access to the internet. Happy to be proven wrong though.