Everything posted by joergalv
-
Chaseplane
Well, I think it’s not easy to reduce complexity for something as complex as the MSFS camera system. Have you ever tried to configure a controller for the Drone Cam, using MSFS default config dialogues ?? Well.. a nightmare from my perspective. To copy a camera, press ‚ALT‘ on the keyboard, this will bring up ‚copy‘-icons for the cameras. Click the copy symbol of the ‚source‘ camera to create a new one. The ‚Pen‘ Button of the active camera will allow you to adjust the settings of any camera. There is an excellent tutorial in the app which will guide you through all those settings. The import feature works for sure.. but of course, someone needs to create and provide a camera for that aircraft first.
-
AI spotting with Chaseplane?
If you consider the purchase of Chaseplane anyway, yes you can save 'your' preferred spotter spots as a world camera in Chaseplane.
-
Viable option to replace ChasePlane in FS2024
Flow was just released for MSFS2024: https://parallel42.com/blogs/news/release-42-flow-pro-and-flow-essentials-for-msfs-2024-on-pc
-
Fenix A320 - severe stutters in '24 SU3. Any ideas?
joergalv replied to AJZip2's topic in Virtual Reality (VR) for Microsoft Flight Simulator (2020/2024)I don't use VR, but can tell that with my RTX 3060, and FG-Mod in 2024, enabling/disabling fps cap (MSFS 2024 internal or external via NCP) is night & day difference regarding stutters. I have FPS capped to 30.
-
Frame Gen mod in SU2?
I had the same. 3060 card. DLL-Version of the FG-Mod. My base config is 30fps which is 1/2 refresh rate of my 60Hz Displays. With FG enabled, all fps counter - i.e. MSFS DevMode and CapFrameX/RivaTuner - stayed at 30fps, BUT it was clearly noticable that FG was active, and 30fps a 'false' claim. - much smoother display, you clearly see the difference between 30Hz to 60Hz. might be not so evident when going from 60 to 120Hz(?) - very prominent FG artefacts in the Asobo Cessna. - GPU Load dropped from >80% without FG to roughly 40-50% with FG enabled. P.S. Prior to SU2 beta, FG introduced severe stutter. So did LosslessScaling.
-
2024 links that works in 2024 for FS 2004.
Not using FS2004 anymore but still in my bookmarks and seems to work: https://www.freewarescenery.com/fs2004.html
-
Flight planning web site
quite some options and some new kids leaking around the corner. But atm simbrief.com is the de facto standard, and gives you everything you've been asking for. You'll need to register an account with Navigraph, but don't need a payed subscription to use simbrief.
-
Interesting weather toy
Good find! :smile:
-
Fsssssssst - every minute or so!
might be worth checking whether CPU or GPU fans are kicking in frequently to lower either temperature. especially if you're located in UK, or continental Europe, given the record breaking temperatures we're experiencing right now. Joerg
-
Possible solution to stutters in P3D?
sad to hear, but possible you got an issue with the shader cache. If yet not done, delete the shader cache. P3D v2.5 should run just fine on your rig with a default cfg. Only important tweak: OPTIMIZE_PARTS=1. No other tweaks here. I get 60 fps and smooth as silk. Settings: Unlimited frames, VSync and Tripple buffer enabled. FXAA off, MSAA 8x, TF 16x
-
Possible solution to stutters in P3D?
Great find!! Best one since OPTIMZE_PARTS=1, i'd say. Major improvements here! Almost no stutters anymore!! :smile: Thanks for sharing!
-
View controls without EZCA in Prepar3D2.5
No. Though the EZCA version 1.18 supporting P3D2.5 is considered "beta. Some flaws possible. You'll find all info in the EZCA Forum at simforums.com
-
I wanted vsync, so i dealt with the evil...
Yes. Vsync control to Standard + 1/2 refresh rate in Nvidia Inspector.
-
I wanted vsync, so i dealt with the evil...
Thanks to All. Great Feedback.. So it might be a GTX 680 specific vsync issue :( Just googled 'vsync stutters' .. and the GTX 680 is named in almost every result on the list. A thread about vsync stutters in the nvidia forum is 139 pages (!) long.. so... waiting for a driver fix... and 'sorry' to Aero. :rolleyes:
-
I wanted vsync, so i dealt with the evil...
Aero is off! And it won't be enabled again .. Like most of us Nvidia users, i enabled Aero just after one or two attempts to get vsync working in this new sim. It was one of my first 'corrective' actions ..and well ..Aero On, and vsync worked.. .. good to go.. So, i had Aero enabled and tried to find the sweetspot between EQ / smoothness / fps , et all... for one week. I had good times, i had bad times (sounds familiar?), More trial & error then logical approaches.. Yetsterday i decided to stop tweaking, but wait for LM to deliver an update instead. I just wasn't able to get it right. Stutters, sometimes, more, sometimes less, Really bad! Not to talk about the inability to make smooth turns with my head using Track IR.. Again: stuttering mess! And all that with 'only' moderate settings... So I started FSX again .. and I was really blown away how smooth everything was. What a difference! Exactly in that moment i started wondering, and asking myself a couple of questions. I just couldn't get it. What should keep p3dv2 from delivering smoothness at least on FSX level. And why should Aero be good for p3d when it's bad for FSX? Has LM or MS improved Aero recently? Certainly not. Bang! I've never tweaked p3dv2 with Aero disabled.. i should give it a try.. And i did.. and i think you should give it at try too... My result for 3840x1024 (!) Vsync: Nope, sorry, still not working, so tearing, yes, but... Tearing; down to an absolutely acceptable limit (Depends highly on your HW & settings You might have to play with P3dv2 INTERNAL EQ settings to bring it down to an acceptable limit) fps: rock solid 30fps, even in complex scenery & heavy weather (tested in FSDT CYVR), Stutters: Gone.. Smoothness: Outstanding, throughout whole flights! AA: Acceptable (room for improvement off course) Aero: Off Clean prepar3d.cfg (TBM tweak is NOT required) External FPS Limiter required! (NI works, DXtory gives slightly better results, i.e. less tearing) P3Dv2 Settings Graphics FXAA: Off MSAA: 8x SSAA: 8x (in Prepar3d.cfg, don't know whether it makes avisual difference) AF: 16x Vsync & TB: Off (Yes!! Turn it OFF!! It won't wotrk, but spoil performance if you turn it on)) Target Frame rate: unlimited Texture Res: High - 2048x2048 Tesselation Enabled Other Scenery sliders are all somewhere in the 'middle' Shadows: Q: Medium, I+E Vehicle: C+R Terrain: C+R Buildings: Cast Nvidia Inspector: All reset to defaults, NO AA Enhancement etc.. (i don't see an enhancement with SGSSAA, but only very high fps impact) Optional: Frame Rate Limiter: 30fps For any limiter: Make sure you lock for any of the Adaptive Vsync Frequencies 60,30,20,... to get max smoothness) Vsync will be available without Aero some day.. until then i'll run with the above config.. If you test it, please report back..
-
Back to hell
OOM hunting in FSX is all about CONSEQUENTLY adjusting your settings.. No HW involved.. I'd bet this game didn't change with P3Dv2 Unless you've already testet ALL of the following TOGETHER: go down with REX clouds not higher then 1024x1024 reduce the cloud draw distance to 60mi max Sceneriy complexity, AG vegetation & buildings to normal TEXTURE_MAX_LOAD=2048 LOD=4.5 Again: Do it consequently, or you won't succeed.. Once your settled you might be able to increase SINGLE parameters, but not all. You want to capture the GS for a safe landing? .. you'll need to capture it from below ;-)
-
No vsync: tearing spoils it all right now
according to P3D Support Aero needs to be enabled to get vsync to work.. .. just enabled it .. and they are right ;-) Edit .. WOW!! Enbaling Aero Made My Day !!! Go for it!
-
RAAS still inaccurate
Which Version? makerwys 4.672 produced odd results for me too. Reverting to 4.671 solved the issue.
-
Drivers for FSX and PMDG Aircraft
might be caused by scenery layers sorted in a wrong order (?).. there is a rule how landclass, mesh and other layers should be "stacked".. unfotunately i don't remember at the moment..
-
Anyone using NGX + GTX 670/GTX 680?
I applied Kostas Tweak - thanks for the link - and, according to the first Q&D results, see an improvement. I still have some stutters though, especially in turns. Might be related to the resolution 3280x1024. However, the overall experience is still fine for me and fluid. I'll might make another test with only one monitor (1920x1080) on the weekend. However, any result i'll achieve will not be able to stand as a valid comparison between a 580 and the 680.
-
Anyone using NGX + GTX 670/GTX 680?
I can't judge against a 580, but compared to my old 460GTX the 680 is a major improvement where GPU power is required i.e. rendering clouds, antialiasing and texturing. Native FSX 3D performance seems not to be improved too much since it's totally CPU bound as we all know. Note: My resolution 3840x1024x32 VSync stuttering: I' d rate it as dependent of the nhancer settings. I noticed that different settings will give different 'stutters', though wouldn't rate it as problem, and don't see a decreased vsync performance compared with the 460. Where do I find Kostas tweak? If you'll put me in the right direction I'll try those settings and let you know ....
- Can I Step through each leg and have them shown on the ND ?
-
A/T ALT HLD bug?
No bug, according to FCOM Vol2 4.10.2"... A/T engages automatically when following AFDS modes are engaged: ... ALT HOLD ..." and more detailed in FCOM Vol2 4.20.10 "Autothrottle Engagement" "Moving the A/T Arm switch to ARM, arms the A/T for engagement in the N1, MCP SPD or FMC SPD mode....." and then later it depictes exactly your scenario "... if not in a VNAV mode, engagement of ALT ACQ or ALT HOLD automatically engages the A/T in the MCP SPD mode" edit and of course, no procedure recommended to be applied on the ground ..
-
[Poll] - CTDs statistics and hotfix installation
Hotfix3 was the first fix i applied. Introduced stutters and other minor oddities. No CTDs, no severe freezes though.Made a compelete deinstall of the NGX, and deleted DEM folder manually following the deinstall routine.Downoaded the latest BasePackage Full Installer and run it. The NGX is fluid and stable again now.It took me <20 minutes and should be worth a try for everyone encountering stutters after applying the standalone HotFix3.
-
Nvidia releases revised Fermi 460 GTX in 2 versions
joergalv replied to SpiritFlyer's topic in Video Hardware: Monitors | Multi-Monitors | Video Cards | Drivers etcJim,back in the FS9 times i tried all 3 options, ending up with one clear result: Option 2!1) SLI did not support multi monitor setups 4-5 years ago, and even with only 1 monitor, did not improve FS performance.Don't know if SLI now supports multi monitor setups, but am still convinced that it brings no big performance improvement in FSX (if one at all)3) Works, but some drawbacks and: not required for what you'll try to achieve.Main issue: You'll have to maintain different FS installations and keep them synced with all sceneries et all. Yo'll also need multiple licenses for concurrent use of multiple installations of FS and Add-On products.2) I'd recommend Option 2 !! It's flawless, it works. You'll be happy. I am since a couple of years! The GTX460 with 1 GB is capable for such a resolution.Best Regards,Joerg