tkyler

Was doing some testing and I decided to record it. I was using the computer mic so it picks up keyboard and mouse clicks and some low audio from the computer speakers. Video doesn't do it justice at 40+ fps and high resolution. If you watch in in HD, you can see how much clearer things are.

anybody seeing the ADF / RMI not working? I've tried several aircraft and the NRMI12 indicator won't respond, even though the bearing dataref is correct...the needle just parks at the 3:00 position...this is the default planemaker gauge BTW.

Nothing to show, but the work does goes on...mostly behind the scenes engine stuff. What you see in the last couple of screenshots will be what you'll get visually. I just need to make everything work as it should from a cockpit interaction point of view.

You know we are all different people...different personalities. We have differing priorities, differing ideology, differing goals. Trying to demonstrate a point to someone who is working off a differing foundation is like trying to derive an equation for free-fall when you disagree on the gravitational constant. There can be no resolution. For some, the org is a repository of resources and comradeship. For others, it is a huge opportunity for marketing and sales. Both of those sides exists and each get out of it what they're after. The only point you can argue is your own perceptions. WarpeD likes the resources, Nicolas likes the potential customers (i.e. all the flyers). To me, it's a mosh pit. On another note, I don't think its good to rant outside the rant section though so I'd encourage (while we're still a manageable community) any further or more passionate posts to move over there should someone feel the need.

Well it certainly couldn't hurt. Do please upload them....until the day we can share assets here in a more organized manner, but it has to start somewhere!

Interesting reading on the future http://www.eaa.org/news/2011/2011-03-24_GarminGTN750-650.asp

AG scenes have a new *.agp file extension...the objects that make up the scene are OBJ of course.

The scripts I'm referring to are for scenery and not aircraft.....the days of "one script fits all" is gone. It's possible these scenery scripts will get ported to V2.5 of Blender, but no idea when. For aircraft, I'm going to probably stay hard headed and stick with the aircraft scripts I use now....the original Marginal work, improved by BenR and BenS and possibly some other Bens I don't know about. They just work, like a hammer! ....though eventual porting to 2.5 would be nice to keep with the times and future improvements to Blender. It'll probably happen eventually.

3.8 man...3.8 Seriously...I'm going to use 2.49b. That's what the scripts are for. If they get ported to 2.5b/2.6, the usage will probably be the same though so the information will still be valid.

Well I just finished up my rough outline of tutorials and there's about 15 or so of them. So far, there will be four for scenery 1.) An overview of scenery in xplane...hierarchy, file structure, elements of scenery and tools 2.) Basic scenery creation using WED and the included library elements...no 3D needed. 3.) Intermediate scenery.....basically custom 3D object creation 4.) Advanced scenery, which covers the AG tile scene system, a bulk object exporter, conditional OBJ commands and orthophotos....(help Eric!) What I'd like is for folks to be able to just go through them and be able to get all the information in one spot. If nothing else, we'll have a "information desk" where I can direct people to the correct locations for resources. Once this gets up and running, I'm going to be pretty shameless about asking people to point in this direction when it comes to others wanting scenery or wanting to develop scenery. The time has come for scenery to get going in xplane.

x-plane's 3D object format with the extension *.obj is NOT the same as the wavefront *.obj extension. The only 3D applications that have reliable x-plane obj exporters written for them are Blender and AC3D. You do not need to work in Blender if you work with sound "gaming" principles...i.e. polygonal modeling and UV mapping. Now I WILL say that the Wavefront OBJ format is one of the more reliable formats for getting your work into blender with textures intact....so for you, you're workflow would be model in Maya, export from Maya via wavefront OBJ (Lightwave LWO works well too) and then import your OBJ/LWO into blender so you can run the export scripts to yield a xplane *.OBJ format Once you have xplane's OBJ format, you can use WED to place. As much as everybody loathes blender initially, if you plan on doing any reasonable amount of modeling for xplane, there are several advantages to working with it. Once I get around to doing some tutorials though, I might be able to do some on alternate workflows.

No....and I'm not planning on doing it either. As soon as I am able, it is my intention to make this venue THE place for serious development information. I've removed the content above as it was mostly intended to answer your question Simon....and even though we have shown a bit of scenery on xplane.com, we still are limiting the information we let out. It's' more proper to say that WED is a replacement for OE rather than Blender. Blender will be suitable for building very small scenes that you'll place with WED.

Simon.. I can't think of any reason ........ EDITED: content removed

Oh I was just giving Ola a hard time, lightwave is fine. You can use Lightwave to model and texture...and then import your work into blender for arrangement and export. These features will be available a bit after V10 ships. We are developing the blender scripts and workflow as we work on V10 and documenting it. After V10 ships, we'll have to work on WED a bit to get it user friendly and then we have documentation to write. I'm also hoping to do a significant amount of video tutorials to demonstrate the system and workflow. We're all quite excited to have the community begin building x-world. If I were to give you any advice about organizing your work in lightwave...I'd simply say use as few textures as you can, pack as much into a texture as you can so that many objects share the same texture. We'll be providing a lot of "generic stuff" for scenery but really specific buildings will have to be custom...so it would be wise to cram as many buildings into one texture for a given area that you can.

OK...Here's the list I compiled today...scratched off items got completed today. Get GPS power working Get Radio switches working Add Gear Door animation Setup controls to initial positions: cold/dark & running Gyro slave switch glass animation Yoke show/hide/animate annunciator test lights fire handles and simulation AP console texture fix ADF draw order wrong Add ADI flags, animate to DC power Overhead switch illumination HSI AP direction knob issue landing light animation Overhead controls plugin logic Set more panel light regions to respond proper to rheostats So once this list starts to dry up, you'll know I'm really close....though there's some good programming associated with the overhead switches. Now if some of those things on the list don't make any sense to you...since they're working in the current version, recall that I redid the entire plugin from scratch and have to reprogram a few items to utilize the new system. As things stand now..for relatively normal operation in good conditions, everything is working properly. So a few more special touches and we'll be there....and what's an update without a screenshot. It's the same old panel shot...but you might note that the panel as a whole has a much cleaner, clearer and consistent look....and don't forget you get a fully featured Garmin GTX330 transponder...a lot better than the V1.1.1 piece of junk.

It's not a glitch in x-plane, I explained this to you in my post and I am 100% correct. The mixture ratio is your problem. if you do not use the ignition switch, the mixture will be zero and the engine will not start. You have been given the answer and are not listening. Turn on the mixture dataref and watch it yourself if you don't believe me.

Guys...Reply 2 is enough of a clue. The mixture ratio is probably zero, which austin sets on cold and dark situations. "mixture ratio" is Austin's very generic way of adding fuel flow to the engine...so you have to figure out what button/lever controls the fuel mixture. If you have electricity (which you do to have the starter work) and the mixture ratio is 1 , the engines will start. On "The Jet"...the ignition switch ..if you click and "turn" it to start...it'll set the mixture ratio to 1 and then the engine will start using CTRL-1...however, if you do not do this step first with the ignition switch, CTRL-1 will not work.

Not at all, you bring up valid concerns that other may have..and we'll probably relocate these posts soon anyhow...I've never been able to move a post where I want it so I'll see if I can get smarter admins to do it.

A few points: rather should be: because peace of mind is relative, I have plenty peace of mind with it even for the two software products I own that use activation....one over five years now, trouble free. Absolutely... it's your own decisions that matter. We're simply dealing with different personalities that must be respected.

Thanks dainja556...I will have copy-protection, but I'm not sure what your definition of active is. For those who aren't "up to date" on our current copy protection scheme, a bit of clarification might help you decide if we're too active or not for you. Please note that the system used on the current MU2 is NOT our latest system and the new MU2 update will utilize our new system. We create a local license file during installation commensurate with your purchase and then leave you to your business. We do this only when you run the installer program. After that, you're on your own with no intrusion from us. You can run the installer on another machine or re-run it if you upgrade your hardware or OS and we'll create a new license for you. It's my bet that a customer who bought one of our products using copy-protection....would be able to go, at minimum......2 years (3 on average) with nothing more than running the installer and entering their x-aviation email/password no more than 3 times in that time....and that would be for cases where they changed machines or OS. At least 95% (probably more) of customers are in this category...and if someone won't buy because they oppose the copy-protection I've chosen, then in my opinion, they're missing out on a great product. I certainly deal with more restrictive software protection every day on my machine and I bet we all do. I think sitting through a single 30 second commercial on CNN to see a news clip takes longer than the amount of time I'll spend dealing with my own copy-protection in 3 years. I can't remember the last time I dealt with my own MU-2 license...certainly been over 2 years now. (I'm subject to my own protection....you know....don't put anything on others you're not willing to deal with yourself, etc.) OK...defense of OUR protection over...certainly it's been beat enough. The MU2 is getting attention, but there's still a bit of work to do beyond the visuals. The entire plugin has been rewritten from scratch and I still have a few systems stuff to work out AND making concessions to hardware users is proving quite a challenge. It seems that having everything for everybody is just tough...meaning mouse and keyboard users vs. hardware users with button and switches vs. hardware users who use the keyboard for buttons and switches, etc. I am still undecided on how to allow things to be actuated. In the longer run, I expect to have a configuration screen and multiple options, but all this tech takes time to build...and at the least, I design my stuff to be reusable nowadays so that future products can have all the good features without the long dev time. Soon...soon!

Ola....imagine a world where you can take these 3D pieces your building...and arrange them in Blender....and each object is a separate OBJ with it's own texture....and you can use all these OBJs in Blender to build a "scene"...and can export with one command..... and place that scene in WED with one click and your separate OBJs will actually sit on the ground....such a world is soon to be a reali....oh wait...you're on lightwave...nevermind! Jason...you're on drugs! The caravan...she's-a still alive! and getting attention again.

Nick...this doesn't tell us if the random acf you were downloading were ones that had plugins. Does it run with the default install? Does it crash with a add-on that uses no plugin? How about with the resources > plugins devoid of any custom ones? Certainly a plugin is probably the issue. If you're on mac, launch xplane and when you get a crash, you should get an apple crash log...you know the dialog that says "report / ignore". Click "report" and it'll bring up the crash report..which you can copy and paste the text into a text file....post that also and we'll have a look

maybe....I'll tint the color towards the end of the night texture work based on photos I have of night ops in the MU2.

State of the night texturing

Not objectionable at all if it's your own project...but it's my opinion the effort would outweight the reward very very rapidly. "Adding in 3D" to any cockpit object is not as straightforward as it sounds....we explored that idea long ago but the *.obj format doesn't really lend itself to those kinds of additions. It's possible for sure...but it would be an exercise in "can I do it?" I think. captaind172...I agree that variations would be nice and I certainly hope to get to that point. There is a G600 equipped MU2 though that is really nice.