GullWings

I was mainly referring to how much more VAS consumption there is with this product compared to the more efficient TBM850 and Phenom300 products from Carenado®. w.r.t. CG's I am pointing to entries and gauges commented out, whereas SVS which should have been, and was not, despite the fact that I didn't have SVS installed (a real FPS killer, anyway).. Examples cited are... //-------------------------------------------------------- //[Window08] //Background_color=0,0,0 //size_mm=700,800 //window_size= 0.344, 0.800 //position=3 //visible=0 //nomenu=1 //ident=10290 //gauge00=DA62!TestWindowsAircraft, 0, 0, 700,800 //-------------------------------------------------------- [Vcockpit01] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$Panel_1 gauge00=NAVIGRAPHDA62!Proline_Config, 0,0,10,10 gauge01=NAVIGRAPHDA62!Proline_Common_Update, 0,0,10,10 gauge02=NAVIGRAPHDA62!Proline_C_Patch, 0,0,10,10 gauge03=DA62_G1000!G1000_CONFIGDA62, 0,0, 1, 1 gauge04=DA62_G1000!COMMON_UPDATE_G1000PFD, 0, 0, 1, 1 gauge05=DA62_G1000!G1000_PFDDA62VC, 0,0,384, 250 gauge06=DA62!ToggleCARG1000, 32,0, 384, 16 // SVS gauge07=Carenado_G1000_SVS\WebSimSVS!WebSimSVS,1,1,1,1,C_G1000.ini (THIS SHOULD BEEN COMMENTED OUT IF 'SVS' NOT INSTALLED) //-------------------------------------------------------- [Vcockpit02] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$Panel_2 gauge00=DA62_G1000!G1000_CONFIGDA62, 0,0, 1, 1 gauge01=DA62_G1000!COMMON_UPDATE_G1000MFD, 0, 0, 1, 1 //gauge02=DA62_G1000!G1000_MFDDA62VC, 0,0,410, 267 //gauge01=EMB505_G1000N!COMMON_UPDATE_G1000MFD, 0, 0, 1, 1 gauge02=DA62_G1000!G1000_MFDEMBP100VC, 0,0,410, 267 gauge03=DA62!ToggleCARG1100, 64, 0, 400, 64 gauge04=DA62_WX!SYS_DA62, 0,0,1,1 //-------------------------------------------------------- [Vcockpit03] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=512,512 texture=$Panel_3 gauge00=CarSound_DA62!CarSound, 2,2,5,5 gauge01=GAUGEDA62!Gauge_UPDATE_DIG, 2,2,5,5 gauge02=DA62_G1000!G1000_Audio, 421, 0, 91, 512 gauge03=EFISSTBYDA62!EFIS, 205, 0,214, 496 //gauge04=DA62!ToggleCARG1100, 205, 0, 214, 100 But then again, the author might have been in a hurry. ___________________________________________________________________________________ If you are upset by my comment, I offer these some extra and re-arranged cameras for each of the Da62's 7 seats in apology... [CameraDefinition.006] Title = "Middle Back Passenger" Guid = {0456199A-99D4-11DC-B263-66CC55D89593} Origin = Virtual Cockpit MomentumEffect = Yes SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.69 SmoothZoomTime = 2.0 ZoomPanScalar = 0.4 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.35, 0.05, -0.85 InitialPbh=8, 0, 0 [CameraDefinition.007] Title = "Left Middle Passenger" Guid = {E575D28A-EECF-4CF8-9905-9EFA317D2D50} Origin = Virtual Cockpit MomentumEffect = Yes SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.69 SmoothZoomTime = 2.0 ZoomPanScalar = 0.4 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.00, 0.05, -0.85 InitialPbh=8, 0, 350 [CameraDefinition.008] Title = "Right Middle Passenger" Guid = {098B8C5B-DA7F-435E-B01A-F8C9B3C8C918} Origin = Virtual Cockpit MomentumEffect = Yes SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.69 SmoothZoomTime = 2.0 ZoomPanScalar = 0.4 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.69, 0.05, -0.85 InitialPbh=8, 0, 10 [CameraDefinition.009] Title = "Left Rear Passenger" Guid = {144F53B9-5498-45D7-894C-44BCC69F2207} Origin = Virtual Cockpit MomentumEffect = Yes SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.69 SmoothZoomTime = 2.0 ZoomPanScalar = 0.4 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.25, -0.05, -1.85 InitialPbh=8, 0, 350 [CameraDefinition.010] Title = "Right Rear Passenger" Guid = {CBD5909E-1420-456C-93CA-A3AC696799A7} Origin = Virtual Cockpit MomentumEffect = Yes SnapPbhAdjust = Swivel SnapPbhReturn = False PanPbhAdjust = Swivel PanPbhReturn = False Track = None ShowAxis = YES AllowZoom = TRUE InitialZoom = 0.69 SmoothZoomTime = 2.0 ZoomPanScalar = 0.4 ShowWeather = Yes XyzAdjust = TRUE ShowLensFlare=FALSE Category = Cockpit PitchPanRate=20 HeadingPanRate=60 InitialXyz=0.44, -0.05, -1.85 InitialPbh=8, 0, 10 Hope you realise I still love the thing, even with some deficits compared to the VertX® DA62, but that thing has even more irritating issues. Cheers, GW

Why has no one mentioned the bug in v2.0. in FPL, the 1st character typed in (either ICAO or WPT) via keypad (VC or fixed panel) is repeated. This always requires a BKSP to complete the code input and is a real pain in the butt! Carenado® support ticket response was... Uninstall DA62, D/L again and install as Admin. I did that the first time. I did it again. Hey Carenado®...…It's a bug - fix it!

About Carenado VS VertX DA62, for those that might doubt it...a boxed FSX + (SP2) Acceleration, with select weather add-ons (the best still being freeware), plus the ORBX suite (Global, Vector and LC areas, HD Buildings, plus select detail airports), ALL running on a real FAST CPU, plus a decent GPU (not as important for FPS, unfortunately) with a suitably tailored (well tweaked) FSX.CFG, can still deliver a sim experience as good any P3Dv3 or X-Plane11 video I've seen to date. Reshade® and a mix of great and varied freeware and payware aircraft (still the biggest available selection) keeps me satisfied UNTIL the move to MSFS 2020. So how long for a DA62 then? PS: Carenado's DA62 Garmin 1000 implementation is rubbish, even in v2.0. Q: So how can it be even worse than in other prior products like their TBM850 or Phenom 300? Take a look inside the aircraft.cfg and panel.cfg files as installed. It looks like they were edited by an intoxicated individual. GW

They work together just fine, but its better to go via the USB, Then you need to calibrate your toe brakes using the T.RJ12 USB TFRP Calibration software. It's junk but proprietary to Thrustmaster®, but it does set up the ranges for toe brake axes.

Great work thank you. Would you happen to know of a Normal Checklist for the GTN750 suitable for the Carenado® TBM 850 as well? Cheers

Hi Ken, It's good to know that someone else enjoys the native Carenado® G1000 and not have to go for the GTN750, as I too had to learn how to use FLC and implement VNAV correctly in this lovely bird as is. It's a good challenge that I enjoy. It also seems that FSX still has more reliable compatibility than for P3D so far from what I read in this forum. As for the edits to the XML code, you really helped my endeavours in getting the checklists as close as possible to the real thing. Thanks & cheers, GW

Try 'Yaw Damper (on/off) - keystroke CTRL-D, the hover over corresponding Autopilot button to check if affected.

Not possible. I've tried everything using FSUIPC & LUA scripts, but to no avail. Sorry about the bad news. GW

Kenny, I agree with your synopsis on the ability to modify a STAR in flight, however the FLT PLN often puts in crazy WPTS that do NOT match the displayed STAR chosen. This is NOT always the case, but I do think the coding reads the AIRAC database that comes with the Extension Pack incorrectly sometimes. Hard to confirm this though and would take many trials to establish this. Also I find it impossible at times to modify the altitudes for STAR WPTS. I have v1.3 and there are still bugs, but I only wish I could save FLT PLNs, or load native FSX PLNs . I use Little Navmap that has the matching AIRAC database to create FLT PLNs so it really is a great pity. GW

I see where you are coming. I shall try this as a last resort. For those interested, I can report that I tried... [BUFFERPOOLS] UsePools=1 Poolsize=8388608 RejectThreshold=126976 THIS KILLED MY FPS TOTALLY ALL THE TIME! For me at least, I'd venture to say that UsePools=0 is COMPULSORY I WILL PRESS ON.

vortex681, The thing is I know some people say either getting rid of GEForce Experience and/or disabling the Overlay cures this for. Not for me! The thing is, my screensaver working fine with BOTH running (I use ShadowPlay to record). This was the case up UNTIL I installed my Thrustmaster® T. Flight Rudder Pedals. The other thing is that my joystick used to cause this issue too, up until as I said I installed an extra 16Gb RAM! So weird! Have performed all recommended troubleshooting, but NO JOY so far. I am also struggling to get decent FPS (>15) near busy airports/autogen areas. I know my ORBX is a killer, but FTX Global and Vector (it's turned it down for only major highways and roads, bridges only) are de rigour. Perhaps it's my rig that is TOO GOOD , but I really don't think so...It's pretty lame actually... Gigabyte® H370, i7-8700 (Turbo 4.2Ghz), 32Gb 2333 MHz RAM, Samsung® 850 Evo 500GB, Asus® NVidia GTX 750Ti, TrackIR 5, Pablo Diaz HD clouds, custom sky and water textures My CFG includes... [JOBSCHEDULER] AffinityMask=4092 [BUFFERPOOLS] UsePools=0 [GRAPHICS] HIGHMEMFIX=1 D3D10=0 TEXTURE_MAX_LOAD=1024 NUM_LIGHTS=8 AIRCRAFT_SHADOWS=1 AIRCRAFT_REFLECTIONS=1 COCKPIT_HIGH_LOD=1 LANDING_LIGHTS=1 AC_SELF_SHADOW=0 EFFECTS_QUALITY=2 GROUND_SHADOWS=0 TEXTURE_QUALITY=3 IMAGE_QUALITY=0 [DISPLAY] UPPER_FRAMERATE_LIMIT=30 WideViewAspect=True NOTHING SPECIAL TO SEE HERE! I use the recommended NVI profile settings for Win10/DX9 with 1/2 VSync for my 60Hz WUXGA monitor. I am GETTING a bit word not allowed off as I used to get great FPS in the 'old' days (pre Build 1803), so seeing all those videos with all manner of addons (like PMDG +ORBX+ASN) running at 60+ FPS is making me ILL. All I want is to have my sweet and robust 'Boxed FSX + Acceleration' to perform under Win 10 like it used to. It's a hard road so far. I really dislike Win10 forced 'feature' updates. Give me back 7 Pro 64 bit please (for FSX anyway) - Oh, I forgot, it's not supported anymore, well very soon anyway. Frustrating in the extreme! I have a lovely fleet (hangars and hangers full of all sorts of enjoyable flyable stuff), many custom and hand-crafted XML gauges, merged VC panels, etc. I am seeing XPlane 11 taking off so I've held off P3Dv4 with FS 2020 coming up so I am hanging fire. Suggestions to improve my Win10 FSX experience in the meantime are most very welcome. Gulls,

Bnash00 et al, I cannot tell you how much I agree with your reasoning on the merits of a properly working screen saver. It's also a matter of convenient privacy if you have to walk away from your PC, and other people are around. I had the same experience, but it got fixed somehow NOT because of any OS or video driver update, but rather just because I added another extra 16Gb RAM to my motherboard. Before that the screensaver would NOT start. Why this fixed this, I do NOT know. However since then, I installed Thrustmaster® T.Flight Rudder Pedals, and guess what - no screensaver again!!!!! I've tried everything and can attest that disabling any/all NVidia background services, or the GeForce Experience gaming overlay does NOT help. There are a lot of people with HID-compliant game controllers that are having this problem. Check out this bunch of poor frustrated Windows 10 users...Microsoft® Answers NOTHING - Screensaver NOT Working Really it ought to work given the following output (i.e. nothing keeping the PC awake)... C:\WINDOWS\system32>powercfg /requests DISPLAY: None. SYSTEM: None. AWAYMODE: None. EXECUTION: None. PERFBOOST: None. ACTIVELOCKSCREEN: None. I reckon it's Microsoft's issue all the way like something going screwy with relevant registry entries or values, that's my guess. If anyone knows a fix or troubleshooting beyond those 'cut & paste jobs' provided by uninformed 'HB1' employees would be great. Microsoft® have really dropped the ball since Bill Gates started worrying about the world instead of his corporation.

Personally I tend not to use prefixes like that, and particularly that one, still running XP and all. Give Windows 10 Pro 64-bit a go, as it's great for boxed FSX.

hahrg , Did you figure out how to use Transition=YES for VC or Outside view switching WITHOUT that intermediate view you spoke of? I have the same issue when trying to achieve smooth timed view swaps without EZCA or Chaseplane as these are both problematic with TrackIR.

Fielder et al, Another story of woe and partial fixes for someone who still resists giving up on FSX because of their collection of payware, WX & AI Add-Ons, ORBX scenery ($$$s), hours of building custom cameras and XML gauges, FLTs, etc, etc … Having 'relatively tamed' the FPS and graphics, I was confronted on approach to LOWI with a 'blast from the past', i.e. the dreaded "8 minute FSX freeze" !!! I waited it out, as I recalled how, if the sound kept going, it would come back. I then applied an AF to exclude Core 0 / Thread 0 given my i7-8700's 6 Cores (with HT on) [JOBSCHEDULER] AffinityMask=4092 That's seemed to work for now too. Phew! What's next......Microsoft® Flight Simulator 2020 (Azure cloud-based real time AI, scenery, shading and WX)? I must be starting to dream of a time I can actually bring myself to saying goodbye to FSX