Ben Russell

Update is now publicly available. Not official X-A product update yet but it should work. More info here: http://forums.x-pilot.com/topic/6349-gizmo64-1401160029/ Found a bug... -sigh-

Using a command-button will generally be cleaner; - Who cares what the magic dataref values are. - Doesn't matter if they change in future. - Some things just have to be done that way. I think a lot of people simply forget that there's a sim/command system there, the fact that they have names that look exactly like datarefs doesn't really help.

better yet, use commands not datarefs.

http://forums.x-pilot.com/topic/5978-gizmo-1311050205-download/ Download and unzip. Move X-Plane/resources/plugins/Gizmo64.plugin somewhere safe like the Desktop Move the new Gizmo64.plugin from the zip download into X-Plane/resources/plugins/

The update to resolve this memory leak you spoke of IS coming. Please bear in mind the time of year, we all have families, it is not your exclusive right to enjoy their time. I'm sorry that this impedes your enjoyment of your product but I can assure you that I suffer the same things at this time of year for much the same items. That said, it's now the second week of the new year. Perhaps the first real business week for many coming back online. The bug has been found, the fix has been written. We're now in the final stages of QA and making the update worth everyones time. I try to address multiple issues with each plugin update, I hope you can see the value in that. The real world is by no means perfect anywhere you look. It's not an excuse to do a tardy job, it's an observation that best effort is necessarily a human thing and subject to failure, no matter your budget, team size, or brand name. A fix exists and will be offered as soon as possible. (This is public information posted in the relevant thread..) Please monitor the forums for news and updates. Alternatively; an email will be sent to your registered address when an official update installer is available. Thank you for your patience and support.

Ford recalling 465,000 2013 models to check for fuel tank leaks http://www.reuters.com/article/2013/06/03/us-autos-ford-recall-idUSBRE9520LA20130603

Yes. And if you do an intermediate stop for more PAX exchange you'll be stuck in the back of the cabin with only the PAX door for air con... they get very hot, very quickly.

No way man, it's gotta be the PMDG 737 NG.

I believe this note stems from the days of 32 bit Gizmo, which was crap. There should be no conflict between Gizmo64 and modern SASL products. There IS however an outstanding memory leak that I'll have a patch out for shortly; this leak applies to Gizmo64/SkyMAXX... it was Gizmo64's fault, buggy activation scripts. TL;DR: Gizmo.plugin bad. Gizmo64.plugin good.

Clearly a screenshot of FSX.

Leak fixed. No error with Gizmo64.plugin The error was in the Activation GUI scripts that I wrote for Gizmo... The scripts were being dumb about how they loaded the product icon PNG files, they're being reloaded over and over again... Time to put all the scripts back together in "retail ready" packaging again... will have an update to resolve this issue posted as soon as possible. Standby..

This is correct. If you run the Saab without SMP you shouldn't see any leak issues. The leak is definitely caused by code inside the Gizmo64 plugin though.

Confident that I have isolated the offending code causing the memory leak, now to fix it.

Not yet, there's more dev work to do before I bother. This is more of a long term project, with low priority. Lots of other work to do..

Social engineering is the easiest way to hack a security system. It is not your wifes place to verify the sales validity of a third party user and a third party vendor. This IS piracy, no matter what you may think to try and justify it. This is also why we insist upon using a DRM system.

Take care Kris... we'll all be here when you get back.

Would help if you were clear about that in the first place. Thanks for wasting my time. Why is import ignored? 'cause the artists don't want kids ripping off their shit. It's a low-tech form of DRM. No artist with the original content has any need for import. Suck it up.

These are for blender 2.49: https://github.com/Marginal/XPlane2Blender These are for blender 2.5+ and should work in 2.6..... https://github.com/der-On/XPlane2Blender (you do not have them already, or you would not have started this thread.)

Try the new ones! See if they work... they've been worked on for a long time, they should be at least 90% as good as the 2.49 scripts... anything thats missing can probably be hand tuned. https://github.com/der-On/XPlane2Blender

Blender 2.6 changed both the GUI AND the entire scripting API. We had two options: Learn and entire new software app AND recreate the entire script set from scratch. OR Continue using blender 2.49 and add additional polish and features to the scripts we already had 95% of the way to perfect. Blender 2.5+ offers ZERO significant improvement to someone who is already happy working in 2.49 for X-Plane content creation. The updates in 2.5 were aimed at new users, unfortunately they left many old users in the cold, hating the new interface. There is a set of scripts for Blender 2.5+ ... they are very poorly named; "XPlane2Blender" ... confusing much? (Two sets of scripts, both completely incompatible with each other, both sharing exactly the same name, call me picky but that's a pretty dumb move by the new authors.) I'm not sure what the functionality is like, I don't think they can match the 2.49 scripts as I believe the Laminar team prefers 2.49 and the old XP2B scripts have had more time invested in them making sure they support all of X-Planes OBJ format options that the artists want. You can find the new scripts here: https://github.com/der-On/XPlane2Blender When building software one must consider how much time will be saved. It is a very big mistake to build new software for every little job. Example: If something takes you 10 seconds longer with the old software and it will take MONTHS to update for new software, you had better be annoyed by that extra 10 seconds at least 200 times a day or I simply do not care about your complaint. Updating software isn't like updating a graphics file format, there is no "Save As"... many times you have to throw almost everything away and start again, you need to have a very strong argument. Put simply, it is easier and faster for you to learn blender 2.49 than it is for me to update the scripts for 2.5 ........ it only starts to matter when you have hundreds of people not wanting to learn 2.49

Returns 10.25 to scripts.

Try 10250 http://www.xsquawkbox.net/xpsdk/mediawiki/XPLMGetVersions

Back in the old days of v7 / v8 XSB was fully capable of using -every- AI slot that you had activated...... it attempted a best match for airframe size/type. Additionally, making XSB use the AI slots is the only way to get the default TCAS instruments to display traffic when online. (XSB makes no attempt to share position data for its traffic via datarefs so this is the ONLY way to get TCAS working afaik.) ...I would be surprised if these rules have changed significantly.

Thanks!

No news is good news. The more status updates, the less actual productive work towards delivery. They'll post when there's something worth posting, like they have done for the last three or four years. http://www.youtube.com/watch?v=U2qrbR-D3GQ