Ronald Griffin

Thanks a lot - just for my own trouble shooting, you are running EZCA 1.17 (P3D beta, or just normal FSX?). Thanks again.

Yes I did, but it's obviously down to my hardware / software configuration then. I will wipe EZCA and start again, if I find the solution, I'll report back here. It must be something specific with my setup, and with all the migration tools, symlinks, and configuration swaps I'm sure it's no ones' fault but my own. Thanks again guys.

Efrain, That's exactly what I mean! And you're achieving this with EZDok as opposed to built in P3D mouselook / FSUIPC? For example, when you press "ML" on the row of view controls in a look, will that allow you to change the view with your mouse cursor when the P3D window is active? Much appreciated!

Hi, Been debugging / testing out EZCA in P3D 2.4. Yes, views work, yes profiles load, and yes most features are solid, however Mouse Look does not seem to function. ML mode does nothing - MMB does nothing (usual pling sound to notify that it has been pressed, moving the mouse simply makes the cursor disappear without changing the view. When editing views, (Numpad 2) ML as always, does not work. Tested: EZCA 1.15 in and outside of Symlink environment. FSX.exe / Prepar3d.exe - fully functioning, however no ML EZCA 1.17 in and outside of Symlink environment. FSX.exe / Prepar3d.exe - fully functioning, however no ML And finally, EZCA 1.17 P3D beta download, same result as above. I'm forced to make the assumption that EZCA is unable to control the view via ML in P3D 2.4. I can only again assume, it needs an updated way to communicate with P3D in that regard. One can dream that such an update will happen, but at this point Marniftarr's disappearance seems to point to that not being a possibility. However, I could be completely wrong - which is why I am here.. does ANYONE have Mouse Look working properly in P3D 2.4 with EZCA? If so, please let me know so I can keep trouble shooting! I am not running Windows 8. I know FSUIPC can be used as a substitute, but I really do enjoy EZDok's way of handling panning, and without it, I'll probably just keep to FSX. :ph34r:

Thought I'd share my latest one here. Cheers!

LMAO! is all I have to say to that shot - I have done a go-around or two myself; but like you I've many times ignored the AI on the runway. I had a friend, we were flying online in the NGX. We were doing Norwegian hops with our VA, and had made our way up north in Norway. We landed on a runway only 6,500ft long that the real airline flew to, my friend managed to hover over the runway and miss the TDZ completely, he still put it down and slammed on max auto brake etc. He skidded off the end of the runway, into the water! It was hilarious. I'd say more go-arounds though!

This is for anyone that finds this while googling for help, or searching, or running into the same problem.THE REASON:SimConnect.dll. This file is responsible for a lot of things, and is generally a nightmare. (at least to me). The problem was that FSX.exe was loading a version of SimConnect.dll that was from the SP1 install - the NGX needs SP2 to work. THE FIX:Download a program called 'Everything'. Search for, simconnect.dll. The only simconnect.dll files that are suppose to exist are the three within the winsxs folder (ignore the ones in rex, or ase folders). Here's a screenshot: http://gyazo.com/f142016f5bf153e3e3ff4687e6295c3e.If SimConnect.dll exists in either; C:WindowsSystem32, OR in the ROOT FSX directory, delete them immediately. This should fix any issues.

Looking really good!

All of those things are done, and it installs the version it wants to install at the end of the install shield. I do not wish to sidetrack this thread, so I will only say that I prefer fixing things as they break and I see the avsim community as a very resourceful and knowledgeable community so this is why I bring my problem here before opening a support ticket. This has nothing to do with being stubborn. I will be opening a ticket if I do not find a solution, or someone who has had the same problem before.Thanks

This is not the case from my experience, wiping FLEXnet folder in programdata removes the registration for the NGX, prompting you to re-enter the key. I've just scanned my registry, the only thing I found was a PMDGSIM1 registry under flexnet, which made no difference after I removed it.

I've tried most of this with no avail. I've re-installed several times now (NGX) - this time I wiped out flexnet's licensing from the folder. This should cause the NGX to ask me for my registration code once more (as it has done in the past). This time however, it does not prompt me for a code. Instead, just loads the model with parts of the engine missing and same story when I load in freeflight, no gauges and no FMC/panels etc. It seems it is having trouble communicating with FLEXnet somehow, any ideas?Another thing that's worth mentioning is no switches inside the VC actually work.

My new place in norway.. My X52 flight controls I can just pull out anytime ;)

Sadly not the case for me.. I'm loading up at the default, I've tried many airports.

Just did a quick re-install (ran as admin, wiped old files). Still no luck in the NGX, this tells me it could possibly be something with my FSX installation, and or flexnet server? If I could find out what usually stops the plane from loading its panels and initializing all of its systems, I could perhaps continue troubleshooting.

Hmm,I've ran all the installers as administrator, it was a clean install so the old .ini's were wiped out manually by myself in one of these SP revisions.

Kyle, thanks for your input.I'm loading from freeflight. I'm not sure if I'm loading any other panel state - I just load the plane fresh as it is, same configuration it came in, only the gauges are not there and the FMC is invisible (shift +3). It seems maybe something has become corrupt, but seeing as how the panel initialization cycle isn't doing it's job I suspect that's the problem, just not sure what it was caused by. It's not a matter of the speed of the ticket - it's just I'd rather not waste your, or my time by doing this. I've got my PMDG NGX loaded with a lot of customization, so I thought I'd save us both some trouble by trying to troubleshoot it first ;)

Hey,It's just I have a habit of fixing things rather than re-installing it straight away. That's why I'm seeing if there are any other solutions. I do not have system restore enabled, so that is not an option for me. Thanks for your input anyhow.

Hello all, Just yesterday I was flying the NGX absolutely fine -- today the NGX doesn't 'initialize' when I load her up. She only loads, and stays with black holes where gauges are suppose to reside. If you need a picture, I'll take one. I don't want to re-install ETC, I've had my fair share of those from the initial release, and I've probably used 90% of my activations due to the product glitching or whatnot. I really don't want to have to sit through a support ticket to get more activiations.Any input would be great, don't want to have to re-install the bird.

In response to your question for lights, from what I understand and have been using for years now is (and correct me if I'm wrong):If it is dark, I will usually always keep my logo / wing lights on below 10,000ft. (This includes when I'm parked or during a turnaround at the gate.)whenever engines are on / going for engine start, anti collision should be on.Pushback - after ground crew is clear, rwy turnoff/taxi lights onRunway entry (Day) - Fixed landing lights ON - Strobes & Steady ONRunway entry (Night) - Fixed and retractables ON - Strobes & Steady ONDuring my clean-up, (apprx 3,000 ft? ) I would usually turn my retractables off completely as they do nothing but cause drag. I'd only have these on in bad vis / night time.Upon passing 10,000 I switch my Landing lights off (Fixed) and my wing and logo lights also go off. The rest remain on.Dipping below 10,000 on approach, I switch Landing lights on (fixed) along with the logo and wing lights if night time.When I drop my gear, retractables go out and on during night time ops.When vacating the rwy, retractables go to the retracted position (not all the way up) - this turns them off but doesnt retract them into the fuselage. My taxi and rwy turnoff lights go on. Along with my landing lights (fixed) and strobes going off.When pulling into the gate my taxi and rwy turnoff lights go off, and my anti collision light goes off upon engine shutdown.The retractable landing lights have 3 positions, retracted, extended, and on. Retracted means that they're stowed in the fuselage, while extended means they're deployed (causing drag). On means that the lights themselfs are on. During night ops, or sometimes day ops, they leave them retracted but not stowed, that's probably what you see.The wheelwell light is used for ground inspection.

This. Check the original thread here, http://forum.avsim.net/topic/351513-pax-in-the-ngx/

http://forum.avsim.net/topic/351513-pax-in-the-ngx/

Rather than doing all this, I'd prefer to just actually type the number into the FMC. Makes life a breeze, and if I'm not mistaken, that's what the 'FMC Menu' was meant to do.

This pretty much sums it up.

No one said this was important, it's just a nice edition to the experience, and since their code probably already includes the calculation, like stated, it would be nice to set the max PAX to the max available IRL. Opinions differ, something minor to you might be very important to someone else.

Well let's hope so, it's a major configuration here in EU.