Scramjet333

Here's your fix for massive aircraft lights. After this, the lights become more believable pinpricks of approximately a pixel or two large. It's a bad bug with XSquawkBox (amongst others like terrible aircraft matching), which is already old, dated software. It's a reason why I've begun seriously considering paying for a PilotEdge subscription.

They're working on v1.1, which will apparently include plenty of 3D model fixes (I myself submitted such a bug, Captain Jan replied), hopefully a less buggy FMC, and some other bells and whistles. Best to check the X-Pilot forums.

Hello gents - I was flying the IXEG 733 from Britain to Vienna a while ago, when I realised that my performance suddenly degraded - from 45-50 FPS, the simulator dropped to 20. On a whim, I went to GPU-Z to check the status of my GPU, and lo and behold - the chip was running at a significantly lower clock rate than it ought to be - around 900 MHz instead of my GPU's 1300 MHz. Is this behaviour reproducible in any of your computers? Furthermore, I find it odd that the GPU-Z sensors do not report a VRAM usage value, when they usually do when running other games. See attached screenshot: What gives?

Some newer GPUs can handle X-Plane very well, and are fairly small, as well as very affordable. Case in point: GTX 960 and AMD RX 480.

Thank you very much for saying that, Mario. In turn, I regret having made a mountain of a molehill. Nevertheless, Cameron's rather incendiary replies made me feel quite terrible. I ought to bring it up to him. Fair enough - even PMDG has done it with their DC-6. I use plenty of freeware like 7-Zip, HWMonitor, and try to use the .zip versions whenever available. I feel it's a rather unfortunate trend to tend towards installers, but when the tide goes one way, we have no choice but to adapt and follow. You have a valid point there, Mario. Could we then call it a limitation of X-Plane instead - the way plugins are handled? Hypothetically speaking, could Laminar restrict all plugins to go into the /Resources/plugins folder, to ease updating and have only one instance of each plugin running? I myself have wondered why I had five instances of GroundTraffic running.

I'm sorry, but you mean being baffled by new behaviour, and finding it unnecessary = elitism?

Fair enough. The 737 Classic is a work of art.

Ladies and gents, thank you for all your replies. Before you get out your pitchforks/tridents/assault weapons/ballistic missiles - please hear me out. I have nothing against X-Aviation as a whole, or their products, which I know are truly superior to what other X-Plane developers have offered since. Their customer service, when it comes to updates, is spot-on, and when we request for a downloads reset, barring server issues, is responded to quickly and professionally. However, I have personally seen smatterings of elitism and pompousness from developers and support staff there and even at the x-plane.org forum, who simply say, 'you're the customer, we do it our way, and if you're not satisfied, don't use our product'. Unfortunately, I'm not even an adult yet with a fairly large salary to just write off a purchase and move on with life. I'm in my late teens, and am a conscript who is given a paltry $400 in allowance. I spent nearly a quarter of that in purchasing the IXEG 737; I can't just stop using it or not notify the developers if I feel a decision they've taken is, I feel, wrong - I'm obviously not getting my money's worth, then. As for why I brought this up, the reason was simple - I wanted to keep all my large tube-liners in one directory, simply for organisation's sake: GA planes in one place, fighters in another, props in yet another, and so on. Certainly, as a few of you have mentioned - a relatively minor issue. I just felt that requiring to have a plane in a particular directory was strange, and completely uncalled for at that point in time. I've used X-Plane for six years now, and this was the first time I'd ever encountered such behaviour. I then realised that the 737 installer as well as the updater also placed the Gizmo64 folder in /Resources/plugins/ which was probably the cause for all this. If the Gizmo64 folder had been placed with the 737 aircraft folder, and was installed with the 737, à la how SASL works with Flight Factor's planes, then we wouldn't be having this discussion at all, since the plugin would simply go to its parent directory and perform the update. Now, however, Gizmo64 goes to one place, the 737 must go in another, and we have the uninstaller for the plane in yet another place, in the X-Plane root directory. If anyone has run Skyrim (or any other recent Bethesda game) with mods and add-ons, you might understand why I am being pedantic about directories - a seemingly minor matter. Until a virtual-directory manager came along called Mod Organizer, mods would tinker directly with the game files and result in a terrible mess when several different add-ons, changing conflicting files, were used. In fact, we can look even closer - I (and probably several others of you here) have heard horror stories of how people wanted to change disk drives, or clean-install an operating system, and how tedious it was to migrate their FSX install with all their tweaks, plugins and add-ons over. With X-Plane, we have it simple. Even in this very forum, a short while ago - Tony expressed amazement at how easy it is to transfer an X-Plane install from OS X on one system to Windows 10 on a newer one. I am just afraid that with the advent of installers in X-Plane, we will lose this immense flexibility we have. It's one short step from requiring custom directories, to writing to the registry, to installing in a different directory altogether. I meant no offence to any of the staff and developers at X-Aviation, some of whom have been genuinely pleasant to see in action (specifically Captain Jan Vogel). However, some of Cameron's ad-hominem attacks (calling me lazy, ignorant, borderline stupid, etc.) were genuinely hurtful. If I were truly lazy, I'd simply have changed directories and moved on with life, instead of even bothering to type out such a post. Mario, thank you for a developer perspective, but I really hope that you understand where I'm coming from. My (a customer's) view is simply as such - if many developers do it this way (use .zips, stick to one folder location and keep things tidy), and it follows X-Plane's ideals, then why does X-Aviation have to do it differently and result in headaches for itself and others? Your post here, Mario, puts perfectly into perspective what I'm trying to say. I likened X-Aviation's actions to MNCs because this reminds me of a highly anti-consumer and even anti-OEM policy that nVidia implemented with a driver update last year: notebook GPUs were locked from overclocking. This caused a huge uproar, causing nVidia to go back on its tracks and release a patch to re-enable overclocking. nVidia's reason: laptops are too poorly cooled to allow overclocking to happen. Users' reply: No, we have thick, powerful, well-designed laptops (something like this) meant to push hardware to its limits; some of our products were even advertised for overclocking. To be clear - X-Aviation's actions are nothing like what nVidia had done, but it felt restrictive. That's all, everyone. I hope you understand why I made this post and the one at X-Aviation. Now, obviously, I'm resigned to moving the 737 Classic out of Heavy Metal, and creating a 'X-Aviation' folder just for one plane, or create some sort of symlink. Oh well... you gain some (now we have VNAV without needing a T/D! Excellent!), you lose some.

Certainly, if there's a technical requirement, then that's fine. If you head over to that thread, you and everyone else can see the entire conversation (on page 1 - I'm 'SRSR33' on that forum. I asked for a technical explanation, and Cameron dismissed my request equally rudely. I'm really really disappointed.

Hello everyone, I believe everyone has experienced their fair share of good (and equally bad) examples of customer service. Earlier today, the IXEG 737 was updated to v1.0.6, and I scanned through the list of fixes, noticing that the VNAV behaviour was altered, so that it could be used even without a T/D. I excitedly downloaded, installed and applied the update, only to be shown this window, which cannot be closed or moved around otherwise: I returned to the changelog for v1.0.6, and then noticed this under the list of 'fixes': I then proceeded to the X-Pilot forums, and enquired about this even asking for the technical justification for this hard-coded nature, and while I attempted to maintain my cool, Cameron appeared to become increasingly hostile, eventually ending with: ​ I'm disappointed, to say the least. It might be the last transaction I ever do with X-Aviation. EDIT: I understand that some of you might say: 'but Scramjet333, why do you waste your breath? Why not just put the aircraft where they want it to be and be done with it?' But then that just sounds like the customer bending over to the huge multi-national corporation. I very strongly believe in customer rights, and X-Aviation, as has (unfortunately) been demostrated several times, have displayed this 'you're the puny customer' behaviour over and over again. Take that particular line one step further, and imagine if the 737 Classic required to be installed in C:\Program Files\ or worse, C:\Windows\, or for the Mac equivalents - the /Applications or /System folders. Would you accept it? X-Plane's strength is in its directory agnosticism, and X-Aviation's practices are undermining it.

I really like the new UI - makes X-Plane look like the ultra-professional sim it really is. Not that the current UI doesn't look nice, it just has a slightly dated, Mac OS X Tiger-esque look to it. Now, if only they fixed the weather. I still haven't seen a decent towering cumulonimbus, even with the new SkyMaxx Pro.

The X-Plane 10 autogen since 10.0 has always used OSM - it's just that the authors' interpretation of the data was worse than what W2XP does (similar to X-Plane's default weather and Real Weather Connector). The third-party implementations are just greatly improved versions of the original, which has great potential.

Excellent - I have been looking forward to this for a long while. It may not be a day-one purchase for me, since I just burnt 90 bucks on new RAM, but I'll probably get this in July.

These shots were taken at about FL250, climbing out of Vienna, en-route to Geneva. Noticeable add-ons used were Real Terra Haze, SkyMaxx Pro v3.1.2 (with the 'Fast' clouds rendering, instead of 'Crisp' which is the default), Real Weather Connector and of course, the excellent IXEG 737 Classic v1.0.1. The Austrian and Swiss Alps are visible in the background.

I would love to see a B787 by IXEG - it would be a quantum leap from the 737 Classic, going from a half steam/half glass cockpit to an entirely electrified plane, so much so that even the FMC is on a screen and all the buttons are touch. Something on the level of the QW 787 for FSX in X-Plane would be a godsend. The Heinz 787 has a decent exterior model, but I've been spoilt by the detail and accuracy of the IXEG cockpit; I just can't step back into the 787 any more (or, for that matter, the FF 777).