twincessna340a

Well worth the read: http://forum.avsim.net/page/index.html/_/reviews/aircraft/review-carenado-citation-s550-r2962

Appears with any of the four landing light switches turned to ON. I've noticed this pre-SP1d. Images taken from the default -800W. Lights OFF: https://drive.google.com/file/d/0B25Gw8h8Kl0MOGxFRElLOGxvSjA/view?usp=sharing Light(s) ON: https://drive.google.com/file/d/0B25Gw8h8Kl0MNmlsUVRpT0pNQUk/view?usp=sharing

The last digit seems to be missing in both NAV 1 & 2 radios. Post SP1d full uninstall/reinstall. Screenshot taken from default -800W. ***No Loss in Functionality - Visual Glitch Only*** https://drive.google.com/file/d/0B25Gw8h8Kl0MNkRvMjdWV1d5MG8/view?usp=sharing

Exactly. I've both used the default PMDG tail number (N773ER.ini) and other .ini(s) I've gotten through the Op Ctr., copied them and renamed them for the PTP and manual install airplanes. Both resulted in not fixing the issue.

Yes Tried both with the default and other OC downloaded paints. I incorrectly stated all when I was talking about the -300ER. I haved checked the -200LR and the issue is occuring there as well. However, There is one that is working correctly that I have been flying pre and post SP1d: Lufthansa Boeing 777-F30 Livery Package Author: Ioan Blidariu / PMDG http://library.avsim.net/download.php?DLID=179587 All the other issue airplanes are authored by non-PMDG staff.... I am still getting the "FSX Missing livery entries detected: PMDG 777 - FSX" notification with this one, which I simply have been ignoring.

Tried it with the automatic and manual installs, sill doesn't work. I have also tried a couple of other non-PMDG paints which are having the same issue.

Tried to do a manual install with just the texture folder and CFG entires.....still losing the clickspots.

Any development with either Bert's or Janek's mods for compatibility with or updates for the SP2 version?

No go. The 3 liveries below are the ones causing issue for me. KLM: http://library.avsim.net/download.php?DLID=188977 Garuda: http://library.avsim.net/download.php?DLID=188995 Lufthansa (fictional): http://library.avsim.net/download.php?DLID=186496

In any of my 777 airplanes that I used .ptp to install with the Operations Center I have loss of clickspots with several switches on the overhead. This is not an eyepoint issue. I moved eyepoint forward and problem still persisted. Issue also presents when on the 'overhead' view of the VC. I did a full uninstall and reinstall with SP1d which didn't fix the issue. Switches affected (known so far): Battery, APU Gen, EMER LTS Switch and guard, PASS O2 guard and switch, APU fire handle, cargo fire swithes, L R Center and Xfeed fuel pumps

I am also having this issue....I'm using a Saitek throttle button.

Any updates to the profile yet? Thanks!

I'm most exited about DX12 as well, but I'm simply curious about OS compatibility. P3D with DX12 would probably involve an almost total rewrite of the rendering engine akin to recoding instruction sets for a 64-bit version. These aren't switch flippers as most seem to think..... I dream of P3D 64-bit DX12 and SLI *stirs the pot*

It was an indexed image, switching to RGB worked. Thanks!

Obviously Windows 10 is still under development, but does anybody know if LM development plans include Windows 10? They skipped 8 and 8.1 not surprising IMO, but 10 does look promising. Thanks!

I'm trying to edit the Just Flight Duchess 2D panel to make it widescreen, taking it from 1024x768 to 1366x768. With Photoshop CS5 I can change the canvas size but I can't edit the image (it's partially locked) or create a new edible layer. When I tried to do this with paint trying to create a duplicate that I could edit, when I saved it a bunch of color information was lost. This led me to believe I needed to use DXTBMP. This also happens for default FSX aircraft. I also have FS Panel Studio if that helps.

When I load an extended BMP that has a size of 1024x768 into DXTBMP, it re-sizes the image to 1024x1024 and blurs it a little. I have no issue importing DDS files, like from exterior textures. Can someone explain why this is happening and/or help fix this? Thanks!

Mine is working now....weird. Thanks though!

I know how the switch works, it just won't recognize the input. Works in my PMDG 777, but not in the NGX. As I said 'NGX_APU_off' button assignment works but the others won't.

The 'Delta' value in the Axis assignments tab specifies the minimum change in physical joystick movement that causes 'movement' to the throttles in the sim. In lay terms it is the sensitivity of the axis, with smaller values of 'Delta' increasing sensitivity (which can be too much). To find the resolution of your calibration (number of discrete throttle points your simulator is recognizing) take the range of the axis and divide it by the 'delta'.

I'm having issues with the APU switch. I can assign a button for it to turn off 'NGX APU OFF', however I can't get the switch to move to 'ON' or 'START' which is the assignment I want to make. Thanks! I'm using LINDA 2.5.7 with NGX 3.2

Confirmed. This is where I got it to work, 'Exclude THROTTLEn_SET' needs to be UNCHECKED. Now to the sync. Thanks!

I would love to and tried to have it that way, but at least in my case my throttles will jump forward and backward wildly as I advance/retract them. I think this is why: According to the FSUIPC documentation: "If you have more than one throttle, and calibrate them separately on Page 3 of the FSUIPC4 Joystick options, you need to take care with any aircraft panels equipped with an “Engine Control Unit” (ECU) or “Electronic Engine Control” (EEC). The aircraft panels equipped with these are altering the values you send from your throttles in order to keep the engine within set bounds. But they do this by sending the same controls as your real throttles, so FSUIPC4 applies calibration to those as well as yours. If you calibrate with the idle position well below centre (i.e. negative), which is quite likely, as you will want to use a smaller portion of the travel for reverse than for forward thrust, then the “idle” value of 0 sent by the panel will equate to some positive forward thrust. There is no easy answer to this. You will either have to calibrate taking care to keep the idle area centred on the value 0, or disable the Engine Control Unit in the panel." IMHO I believe this is the reason that Saitek throttles are finicky with PMDG as I assume the ECU or EEC is fully simulated (someone from the Dev team please correct me if I am wrong!).

I am making a renewed effort to use my Saitek throttles with the NGX and 777X. My specific question is for those that use Saitek throttles with PMDG what "Delta" do you use in the 'Axis Assignments' page in FSUIPC? The default is 256. Both my throttle axis are setup as follows: Reverse: -16193 < 0 Idle: 0=< 2476 Max: 16192 I am going for smoothness (and without using 'sync pos' as much as possible) and I feel that 256, which equates to roughly 53 throttle detents, is a bit small. Thanks! I DO NOT want this turning into a debate or complaint thread. I am seeking advice.

I didn't ask about the -8, but RSR confirms anyway: