Thomas_Kenobi

Agreed, best thing to do is to test things for yourself. Get a monitoring software that can log processor and memory load for both the CPU and the GPU and see what results you come up with. Then you'll have a better idea of where the bottleneck is in your system. The dev team have presented analogies between the performance of MD11, 747 and the NGX, so you could use one of those, if you have them, as a baseline. Or you could simply wait for the NGX itself. :)

In short, none of them. I suggest you expand the poll or include an "other (please specify)" option to make it more representative of the variety of opinions here.I for one, think that we are certain to see massive improvements in graphics anyway, for ATC and multiplayer we have RC and VATSIM already, navdata for navigation data, vroute and others for flight planning, AS and REX for clouds and weather. Slopping runways would be really nice. I just saw the runway at Athens during a recent flight out and I was surprised by how visible the slope actually is. Still it's not the most significant improvement I'm expecting from Flight.If I had to pick one, I'd say a modern engine, built from scratch, freed from the restrictions of backwards compatibility, optimised for modern hardware.

These news shouldn't come as a huge surprise to anyone. It was pretty much obvious that we wouldn't see a release before Xmas.I for one am getting anxious for public beta. I've started warming up to the idea of vulunteering for it, tedium of bug-finding and testing notwithstanding.

Those screens look quite impressive. They seem to have improved every aspect of ground representation like mesh (the mountain-tops in particular look very nice), shorelines, ground textures. I also like the realistic looking forest and the small streams. Hopefully the break with past FS versions will allow them to optimise the code, so that we can actually run all this.I for one would like to see a major airfield next.Here's to hoping!

@OP: Many thanks for posting these. Moonlight (the silverlight version for linux) is the buggiest mess you've ever seen, so I can't access the official site.

Great game that one! Timeless classic! It looks simple, but when you start realising all the things you can do with rail lines it's outright amazing.

Ok gents, let's not make this into a 777 vs Shared Cockpit competition. :PI'm sure that if it comes to that PMDG will do a market analysis that will consist of more than a forum poll. Plus I doubt implementing this is the same amount of work as building an entire plane sim from scratch.Regarding the demand for a shared cockpit functionality now. It's essentially FS2Crew taken to the next step. And as far as I know FS2Crew is selling nicely. This could really be the next big step in our obsess.... err I meant hobby :(

Thanks for the update Ryan. I take it then that the possibility of seeing this for NGX still exists. That's good news.

Thanks for sharing this. It sounds like an amazing experience! Thanks. So... any devs willing to dispel the uncertainty with some info on whether 737NGX will have this? (I'm guessing if they wanted to share this they would have already, but it's worh a shot)

Well since Maddog has this implemented it is definitely feasible. Anyone knows how they did it? Did they provide their own utility or did they use FSX's shared cockpit functionality?Etienne could you post a link to the original thread that Tabs quote is from?

I was hoping it might be possible to do this using existing software, without PMDG having to write new code for it. Thing is I've never tried something like this before so I came here to ask for some expert opinion on the matter.

An interesting possibility has been brought up in the PMDG FB page. Namely that of using FSX shared cockpit feature (or some other means) to fly a plane cooperatively over the net. This is the thread in question:https://www.facebook.com/topic.php?topic=479&post=2869&uid=165758250130634#post2869I think this would be a rather exciting direction for our hobby to take. If the technical aspects can be solved, I'm sure a lot of people here would be interested.What do the PMDG devs think? Is this feasible? Could it be achieved in some other way other than FSX's Shared Cockpit (off the top of my head: using Virtual LAN and WIdeFS)?

A note for people who want to receive notifications of PMDG posts without having to read through all the discussions in this thread, but don't use Facebook all that frequently (or at all). The Facebook wall page has an RSS feed. So you can subscribe to it with whichever RSS Reader you prefer and it will let you know when new posts have been made.

Reading this thread I'm getting positively jealous! I'd love to get the QRH, but for a uni student it's a bit pricey even on its own. Add the cost of shipping it to Greece and it might be cheaper to wait for NGX and have the pdf printed and bound myself.... Sometimes I really hate shipping companies...

Solution Found:I found the solution in a post by Mr. Kalamaras here: http://forum.avsim.net/topic/122156-fsx-trusted-dll-modules-issues/To Moderators: Might I recommend Mr. Kalamars old post is stickied or linked to? He says he's added an article to the wiki, but the wiki doesn't seem to be working. This is a bizzare problem that can't be solved without knowledge of how Win handles dll validation, something that not many people have.Also I found a thread of another who had a similar issue a few years back: http://forum.avsim.net/topic/57845-gauge-errors-in-fsx/

Yes I did work with the fsx.cfg file in AppData.The interesting thing is that after I reinstalled FSX and first launched it, it didn't ask for permission to load FSUIPC, even though it was present in the modules folder and even though the configuration files were the new ones installation placed there. FSUIPC didn't appear in game until I manually run its own installer.It seems like FSX has stopped asking me to approve new DLLs loading. Where in the configuration files is this normally handled?

Ok so it seems the problem is a fair deal worse than I thought. I unistalled FSX and deleted all configuration files then reinstalled, but the issue remains. Which means it has something to do with Windows not FSX in particular. Also I noticed that the gauges from the 2D cockpits are missing as well. I think this is related to how the DLL files are loaded, but I'm not sure.I would really appreciate some help, because the next solution on the table is formatting the Windows partition and that will mean a lot of work...Update:I think I have figured out what is going on. It has to do with the certificates attached to the dll gauge files. Once I added Microsoft's certificate to the list of Trusted Publishers in Internet Options->Content->Publishers the default King Air started working fine again. It would seem Windows has started rejecting DLL files if they don't already have the certificate that accompanies them listed as trusted. This might have been changed by one of the latest automatic updates.Does anyone know how this can be fixed? I would very much like to go back to the things as they were. It's a bit of a hassle having to add a certificate every time I install new gauges and some publishers don't include certificates at all (e.g. freeware, etc...).

Thanks for the tips. I just tried rebuilding the fsx.cfg file and applying the gauges_recovery_fsx fix, but neither helped. Unfortunately the problem remains.

I've been having a peculiar problem with VC gauges in FSX. Specifically in some aircraft (e.g. the default King Air) the gauge DLLs have stopped loading so that when I open the VC I see blank. On the other hand, other aircraft (e.g. the default 737 except the radio stack) seem to be working just fine. I have no idea of where even to begin troubleshooting this. The only thing pertinent that I can think of was that, just before this problem started, FSUIPC started complaining that it couldn't verify the dll signature and didn't run properly. Reinstalling wouldn't help. It recommended that I check the cryptographic service is running (it is) and that I haven't set Pete Dowson as an untrusted publisher in Internet Settings. I hadn't, but I added the certificate to the list of trusted publishers and that fixed the FSUIPC problem, but not the rest.Any help would be very much appreciated. I'd rather not be forced to reinstall FSX from scratch.I'm enclosing a screenshot of the default King Air as a demonstration of the problem.

:( :( :( B) I laughed to tears with that one!!

:( :( This one deserves classic status!

Anything about the availability of the manuals in eBook formats? e.g. epub, mobi,...It would be really helpful to be able to read them in an eBook reader like Kindle. They don't handle PDFs very well and PDFs don't convert to other formats easily, especially if picture heavy.

Typical of PMDG to exceed our expectations handily!I agree that, at a minimum, one could buy the QRH. This is something you might need to have on hand if a situation emerges (you can't quite pause on VATSIM :) ). For the rest I think the PDFs will suffice. Of course if one can afford them, it would be nice to have them in your library!On a slightly different issue. I know the manuals will be included in the pdf format with the product. Are you per chance considering also including them in a more ebook reader friendly format, e.g. epub?

That sounds brilliant! It's great to see detailed random failures implemented. As it is now in MSFS you have no reason to scan the engine instruments or the hydraulics, etc... This should make things far more interesting and realistic.Greatly looking forward to the release! :)

Ok, thanks for the information.