Jump to content

SWVA4420

Members
  • Content Count

    343
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by SWVA4420

  1. Hi Bert....gave it a shot again, and it worked. Very strange, because your instructions were how I was doing it in the past, but it didn't work before....so weird.... Thanks, Jim
  2. Now here's the weird thing - I gave the installers another shot, and all planes except the Premier 1A are working in P3Dv5 without any transparent cockpits as was the case before. I don't know if it's because I updated to v5's HF2 last week (most likely not), but they're all ok now. I have the Premier for X-Plane w/RXP GTN750, so I'll fly it there as it still has the transparent cockpit/no engine starting in P3D.
  3. Hi @Chocorua - no luck, but I gave up trying, ans as far as I know, Carenado hasn't done anything about it yet....
  4. Hi Jesse - thanks, and yup, I've done the patch as well....same result....😖
  5. I've tried this, and it worked for the old C152 and C172, but for all modern/glass panel planes (C525/C550/SR22/C182 G1000/Phenom 100/Phenom300/Premier 1A), the problem of transparent cockpit still exists...I'm at a loss, as I've tried all methods suggested here in the forums. I'm running Win10/32GB RAM/2080Ti w/11GB VRAM.
  6. @cannow - yup, tried that as well, same result, sadly.
  7. Hi - I've tried all of these options for installing the C525 into P3Dv5 HF1, without success. I still have missing/transparent parts of the panel....I'm at a loss....any other ideas? It really seems the Carenado's products are NOT fully compatible w/v5, as I've tried installing several of their planes and all of them had this problem. Note - they're all OK in v4. (Regarding the common textures folder - yup, all 79 items were in it - no difference).
  8. @Reader - that makes no difference for me, unfortunately...problem still exists.
  9. The F1 DC9/MD80 Classic/MD80 Pro all work in P3Dv5 HF1, though the graphics in the MD80s are lacking/flat as they're older planes, but everything works as it should. (And shout out for FSW's Lear 35 as well, with a P3Dv5 installer! Carenado planes have visual glitches/missing/transparent panel sections, even with their "patch").
  10. Thanks, @Chapstick!! - I downloaded the latest version of SODE and now have jetways. Jim
  11. I have no jetways showing at KORD or KMDW, no matter what density settings I use. This problem is in both P3Dv4 & v5, latest updates to both....any ideas why? I also have ORBX global installed, and I positioned the DD Chicago airports below it....it was installed above all ORBX files originally, but again, no jetways either way. Thanks, DD, for making these packages free! Jim
  12. Hi John - updated to latest version as of yesterday, and reported issue to LR was resolved with their latest patch....all's good now @ KSEA. Thx, Jim
  13. good idea, but that didn't work either, mjrheath,,,,probably will just remove and reinstall this copy I have for beta testing.... ps - same problem exists with latest version released earlier today.
  14. No airport buildings after another update try....possible problems in log.txt during scenery loading, and I think this issue has already been reported to LR. Here's my log file scenery load for KSEA Demo Area.... 0:00:36.082 I/FLT: Init dat_p0 type:loc_ram apt:KSEA start at:C18 0:00:57.187 I/SCN: DSF load time: 200129 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+46-122.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 200674 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+48-122.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 342004 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+46-124.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 555469 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+48-124.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 1904418 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+48-124.dsf (182889 tris, 4 skipped for -3.7 m^2) 0:00:57.187 I/SCN: DSF load time: 2612969 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+46-122.dsf (210267 tris, 1 skipped for -0.8 m^2) 0:00:57.187 I/SCN: DSF load time: 2669317 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+46-124.dsf (226326 tris, 8 skipped for -4.1 m^2) 0:00:57.187 I/SCN: DSF load time: 29039 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+46-121.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 3258488 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+48-122.dsf (297281 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 93020 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+48-121.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 217870 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+46-123.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 250658 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+48-123.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 1439699 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+46-121.dsf (178828 tris, 2 skipped for -1470.3 m^2) 0:00:57.187 I/SCN: DSF load time: 1883595 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+48-123.dsf (189314 tris, 5 skipped for -2.8 m^2) 0:00:57.187 I/SCN: DSF load time: 1944386 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+46-123.dsf (224805 tris, 7 skipped for -3576.4 m^2) 0:00:57.187 I/SCN: DSF load time: 2213269 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+48-121.dsf (242887 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 17604 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+47-121.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 25796 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+47-124.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 1852620 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+47-121.dsf (208486 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 2847 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+47-122.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 1651068 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+47-124.dsf (262117 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 1865803 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+47-122.dsf (264501 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 500380 for file Custom Scenery/Global Airports/Earth nav data/+40-130/+47-123.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 W/OBJ: The object Custom Scenery/KSEA Demo Area/KSEA_objects/ConCSlantRoof.obj has a first LOD near distance of 2000.000000 but it should start at 0! 0:00:57.187 I/SCN: DSF load time: 126065 for file Custom Scenery/KSEA Demo Area/Earth nav data/+40-130/+47-123.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:57.187 I/SCN: DSF load time: 2732421 for file Global Scenery/X-Plane 11 Demo Areas/Earth nav data/+40-130/+47-123.dsf (281575 tris, 6 skipped for -18.0 m^2) ----------------------
  15. Hi RXP - that's probably the problem...any idea how to fix, if possible?
  16. Hi RXP - I also have your GTN750, and want to integrate it into those same 2 freeware jets, the Falcon7x and the Gulfstream IV. I've tried the ini file above with ; enable mouse clickspots if true, disable if false (use SHIFT to override) usemouse = true but I cannot click on the screen (the ini file above is specifically for the 7x). The screen renders in the correct location, but clicking on it is not possible. Is there something else that must be done? To tmab204 - what is your ini file for GHansen 's Gulfstream IV? The rendering location and size are definitely different! Thanks, and to RXP - your product is GREAT! Jim
  17. Yes, currently the gauges for all 3 planes are not loading in P3D v4.3...Espen is aware of these problems....
  18. Ah yes, a true master! Love his stuff, hahahahaha! Great entertainment, great creative mind!
  19. Hi Steve, I changed it to: atc_type=Citation atc_model=Cessna And ATC calls it now. I did the same to Carenado's C525A CJ2 as well. Jim
  20. Looks fantastic! One question - will the GoFlight MCP Pro be supported (please?!!)? Thanks, Jim
  21. Hi - Just a thought here: If you have the F1 GTN750, you can get "The Mod Squad's" mods for this plane, and it works great now, much better than the "vanilla" Carenado release! (I highly recommend the GTN750 anyway, as it's a great all-purpose tool and can be installed in any aircraft). Mods can be downloaded from the "SHOWTIME...." thread in this forum below. Jim
  22. Hi All, After migrating from P3D v3.2 (where the gauges worked fine) to v3.3.5.17625, I loaded the plane but the LCDs had an error message, saying the gauge couldn't be loaded. I used the most recent QW757 installer when I installed it into v3.2 originally. I also updated the FSDT addon manager, which prompted for the latest QW757 gauge, to which I answered Yes.... Is anyone else having this problem with this version in this latest version of P3D? I posted this in the QW forums earlier this week, but nobody has responded. Thanks, Jim
  23. Hi - there's a little utility called GWX Control Panel that allows you to block and/or remove Win10 updates, and prevent MS from ramming it down your throat. It's worked great for me on my two FS systems (Win7 home and Win7 pro). When you install it and run it, make sure you select it to run in monitor mode (checkboxes/button-bars to select options). MS will still try to invade your system, but when it happens, the blue-square with the white 10 in it on the task bar notification area flashes with a red circle and a white exclamation point - just open it up and set everything back to "Enable" (reverse logic - if the button says Disable, it's enabled to allow W10 updates....think I got that right....I'm currently on the other side of the country from my systems). Give it a look & best of luck, Jim
  24. Hi - SkySim DC-9 liveries have to be downloaded from their website. There are a few others in the AVSIM library, I believe. Unfortunately for me, I could not get the Coolsky DC-9 to work in P3D v3.2, so I went with the SkySim one....not as thorough as the Coolsky one, but it will have to do in P3D unless/until they update theirs to work in that sim. Fortunately, it works great in FSX-SE, so I can still fly it when I want, as I have both sims installed. The Leonardo Maddog works in FSX-SE, but not in P3D (at least for me). Hope this helps... Jim
×
×
  • Create New...