Jim Robinson

Just loaded up N24RM the Alpine Edition today Ray, thanks very much for the repaints :smile:

Sorry about the goose chase Rod, I guess you ruled out the .db as a problem, lol. I definitely see a performance hit with the .dll in place but nothing like you're seeing, Last night I was seeing mid to low 20s flying into Orbx KPSP in SCA (P3D v3) but it usually doesn't get much worse than that. I hope you can find a solution.

If it were me I'd try deleting the entire FSX\CarenadoNavigraph folder and reinstalling the aircraft, there's a .db file in there that gets rebuilt while you watch the progress bar for 3 minutes any time you update navdata. The installation supplies a pre-built .db file which is why you don't see the progress bar the first time you run an aircraft after installing it. Other CarNavigraph planes will also replace this file upon installation and it will match whatever navdata cycle happened to be shipped with that aircraft. If you delete the folder and reinstall the CJ2 at least you'll know you're using the navdata and .db file that's supposed to be used with it without any remnants from any other aircraft or navdata installations that might conceivably be causing the problem. Since this is the latest release it ships with the most recent navdata. I'm wondering if throughout the process of installing a few aircraft and maybe a few airac cycles something got hosed in the .db file due to an older version of CarNavigraph.dll or maybe an older navdata cycle that may be in a slightly different format than what's currently shipped (and expected by the .dll). No idea if it'll work/help but it can't hurt.

See here, last comment: http://www.airdailyx.net/fsnewsbreaker/2016/4/6/carenado-525a-cj2-v11-released#commenting

With the aircraft parked on the taxiway, no brakes on, adjust the condition levers between 40% and 100% to understand better what they do. At 40% the aircraft will (IIRC) sit still, when you advance them forward the aircraft will roll and it'll require a lot of braking to keep taxi speed under control. My procedure is condition levers at 40% anytime the acft is on the ground, as I roll into position for takeoff I advance them full forward (Ctrl+Shift+F4) and that's where they stay till I exit the runway at the destination airport where I pull them back to 40% again with Ctrl+Shift+F2 (be careful, it's easy to pull them back too far and kill the engines). I'm sure my procedure is wrong, everything else I do is, but that works for me.

There's a pretty good walkthrough of an example flight in "Carenado Proline 21.pdf". It's in your Microsoft Flight Simulator X\Carenado\C90_GTX_King_air folder (or P3D equivalent), starts on page 11.

No, it's just 53 year old logic, if the leg has no length there's no choice but to go direct to either the waypoint the leg begins with, ends with, or anywhere in between, either way you end up at the same place. :smile:

Note there's no leg shown as "active" in green, that's because the leg it's intercepting is between GBN and GBN and it has no length.

See my post #167 at the top of the page for a DTO workaround that will satisfy ATC. You're right about the underlying GPS system BTW and in fact if you enter the same wpt twice in a default FS .pln you can simulate DTO by selecting the zero-length leg between the two identical waypoints in the same manner using the default FS9 GPS. I just did a test to confirm, the problem in that case is of course that you can't modify the default FS flight plan on the fly short of opening it in PlanG or something, modifying it, and then reloading it. That's easily done with the Carenado FMS however without leaving the cockpit. I uploaded a video of the 525 doing a pseudo DTO, watch on YouTube and expand the comment for full details: https://www.youtube.com/watch?v=OKdkMJBmo9I And here's a screenshot of the FS9 GPS in the default Lear 45 doing a psuedo-DTO just for fun:

I've had exactly the opposite experience, I've never seen FLC not capture the preset altitude and I have the throttles rammed to the wall from takeoff till TOD. Seriously, same experience on virtually 100% of my flights with both the C90 GTX and now the 525, no workarounds, no hacks, just press the FLC button, select a speed and wait for TOC. Not once have I seen it blow through my preset altitude. I honestly have no idea where these claims that FLC doesn't work come from.

This is what I've been doing, what you do is press the LSK next to the wpt you need to go DTO, that brings it down into the scratch pad and then just press the LSK again. Now you have the wpt in the plan twice back to back so do direct to and select the 2nd occurrence of it, the FMS will still try to intercept the leg between the two wpts but since the leg between ZIMMR and ZIMMR for example is zero-length the FMS doesn't have any choice but to fly you direct to it. Works, not saying it's correct but it gets the job done.

It has to be entered for each waypoint, once you assign /20000 to a waypoint with the right LSK just hit the same button again to bring /20000 back down into the scratch pad and then you can key it into the next waypoint too and so on.

I guess you have to define "properly", I have about 6 total flights under my belt so by no means have I completely figured everything out. I do have about 70 hours with the C90 GTX though and this is very similar. Here's a typical Carenado Proline 21 flight: I was able to do a flight between KFMN (4-corners) and KAPA (Centennial) using the ZOMBZ1 arrival and GPS Y 35R approach completely under FMS/VNAV control, but the kicker is I (think I) should have been able to select the approach first and then the arrival and transition, however ZOMBZ1 wasn't in the list of available arrivals after selecting the approach. I got it to work by selecting the arrival with no transition at all first and then the GPS Y approach. That's the only way I could get both the arrival and approach into the FMS at the same time. The problem there is the flight plan went straight between KFMN and ZOMBZ where to me it seemed logical one would use the VRAIN transition. I keyed in VRAIN, JIMMR, and JALKA manually assigning them all my cruise altitude of FL270 and also keyed in CABOB with an altitude of 20,000'. The 20,000 was a total guess but it worked out pretty well in this case. The FMS took it from there, all remaining altitudes right down to the runway were loaded into the FMS automatically. After that little software-bluffing exercise it pulled off the arrival and approach nicely. I do have the current navdata incidentally so it's not an issue with an outdated airac. I switched to LOC1 and flew the ILS at the FAF on this particular flight, but I have actually done this approach on VNAV sorta-simulating the LPV with the C90 GTX, it was a little sloppy and there was no glidepath indication but it was acceptable. "Direct to" is indeed "activate leg" but you can actually select some nearby airports from a list to fly direct to. You can also key in a waypoint, VOR, or whatever (after a fashion, keep trying, hopefully carnavigraph.dll won't crash your sim). The problem is apparently that they're using the GPS flightplan here, so just like the FS9 GPS when you go direct to a waypoint it nukes your flight plan. That's speculation on my part, that's what I think is happening anyway and I believe that's the "sim limitation" they keep talking about. Attempting to use "direct to" as "activate leg" I usually find the most logical leg to activate is missing from the list anyway which makes it that much more useless most times. I think VNAV divides leg length by groundspeed to come up with a time value and then calculates a VS that puts you at the selected altitude crossing the next waypoint. If you need to lose 10,000' and your leg is 300nm long it'll put you into a ridiculous -200 FPM descent for 45 minutes instead of hanging at cruise altitude until TOD and then starting down. For VNAV to work correctly you pretty much have to find a published waypoint that you can insert into your plan as TOD and give it a place to start down from, then you'll get reasonable descent rates. That said, VNAV works surprisingly well on published arrivals and approaches because the waypoints and their altitudes are usually set up to give you normal descent rates between them at the speeds you should be crossing them. Does everything work perfectly and exactly like the real world? No, probably not. Is it flyable? Definitely, but you need to learn the tricks and they're not necessarily realism tricks Is it drop-dead gorgeous? Of course, it's Carenado Is it worth the $40 bucks? I dunno, I just buy 'em to get in on the forum discussions :smile: Frankly if they told me I could only have one, either the CJ2 or the C90 GTX, I'd take the King Air. Not really disappointed in the CJ2 though, I like both. Jim

The tooltip on the base of the knob (blue circle) shows altitude, the tip of the knob (yellow circle) tells me I should left click for 100s and right click for 1000s or something like that which is completely useless because it doesn't actually work as the tooltip says it does anyway. :smile: That's what I'm seeing anyway (P3D v3.1).

If it helps you can press Shift+1 to open the 2D PFD, you can also set the altitude on the 2D autopilot window, Shift+3. Lastly there should be a tooltip on the base of the VC altitude selector that shows the preset altitude value, the base of the knob (blue circle) sets 1000s, the end of the knob (yellow circle) sets 100s. Jim

I have the same issue with the throttle, not sure what they did here but if I hold my throttle lever fully forward with force I can usually get more speed out of it and an accompanying jolt in the dynamic head movement. Throttle range seems mostly "crammed" into the upper 5% of my joystick throttle movement, never seen that before on any other airplane. Be careful pulling the power off, you could smack your head on the dash if you're not hanging on. Joystick throttle movement between 100% and 99% feels like the equivalent of deploying a drogue chute! :smile:

Yeah I agree, that thread was confusing as heck. :smile: Condensed version: In a nutshell what the linked post says is if you find yourself unable to click the APPR button to lock onto a glideslope try hitting the VS button momentarily and then try the APPR button again, it should "stick" that time. Jim

I've noticed a problem with clicking the APPR button, same deal as on the C90, the APPR button is simply un-clickable under certain circumstances. See this post though, the workaround is the same: http://www.avsim.com/topic/482338-glideslope-intercept/page-3#entry3367837

What confused me for a while on the C90 is that what shows next to the Preset button on the PFD is the mode you'll be in when you click the Preset button. Use the mousewheel on the upper-inner knob of the DCP to change the preset to LOC1 (or it might say VOR1 if you're not receiving the localizer yet) and load your frequency like you did, when you're ready to let the ILS take over just click the Preset button to put you in LOC1 mode and your glideslope should show up. Hit APPR and ride it down. One caution is that the frequency must be the actual sim frequency so if an ILS frequency has changed between when FSX was released and your navigraph cycle the FMS will show you a frequency that won't work even though it's correct for the real world. Cross check the frequency with the FS map or PlanG and if it's different use the one from FS rather than what the FMS tells you to use.

You can change the speed on the 2D autopilot for now (Shift+3), hopefully they'll fix the VC mounted wheel in a patch.

Try Flight Plan > Import and then choose "fsnavigator 4x blah, blah", navigate to your Flight Simulator 9\Modules\FSNavigator\Plan folder and go for it! :smile:

Sure enough: http://library.avsim.net/esearch.php?DLID=&Name=&FileName=sfp303.zip&Author=&CatID= I don't understand why there would be any question on legality?

By default the ShadersHLSL.cfg should look like this: [Entry.0] Title=Default Shaders Path=ShadersHLSL Required=True Active=True ...so you'd just put your custom cloud.fx in a folder of your choice somewhere, I put mine in D:\P3Dv3 Addon Content\ShadersHLSL and then just added that path as [Entry.0] which gives it priority over default. Like this: [Entry.0] Title=Tweaked Shaders Path=D:\P3Dv3 Addon Content\ShadersHLSL Required=True Active=True [Entry.1] Title=Default Shaders Path=ShadersHLSL Required=True Active=True Jim

We also have the ShadersHLSL.cfg in the %programdata%\Lockheed Martin\Prepar3D v3 folder so you could put your desired copy of cloud.fx into an external folder somewhere, declare it with priority over the default in the ShadersHLSL.cfg, and let REX overwrite the one in the default folder to it's heart's content with no effect.

I believe "Super Flight Planner" can open an .fsn outside of the sim but it's been forever since I've had it installed and I wouldn't know where to get it. I think SFP 3 is the one you want, there was an SFP 4 which was either solely for FSX or had FSX support, it wasn't nearly as user friendly as SFP 3 IIRC.