Goran_M

Oh, trust me, the insanity has set in. I'm just good at bottling it up. I went through 3 different cover pages and 4 different manual formats before I was happy with the 5th one. And this is after the manuals were done.

What Steven said. Also, the update is in progress. I've remodelled just about the entire aircraft. Theo is fixing the textures and then we just have to remap the panel regions and its done. Unfortunately, the Saab is taking up all of our time right now. I'm typing up a 300+ page manual and revising it (5th revision now) and Theo is cleaning up some textures and adding annunciators to the displays. After the Saab is done, we'll get the update for the Sundowner and Duchess done.

I have work to do on my CESSNA CESSNA AND MORE CESSNA manuals. I'll leave you with this final thought.

Hansa, I suggest you stop digging yourself into a deeper hole. That is completely out of line and inappropriate. If you want to buy payware, you have the right to do so. As you said, you are an end user. Let's keep it there. I'm telling you this for your own good.

You claimed to know what it takes to make an add on. I'm giving you an opportunity to prove it. That's obvious. And you proved my point brilliantly. You have the right to choose. But you do not have the right to demand a product. You do not have the right to call ANYONE stupid. Again, exactly. You have the money to pay for a product. It's OUR responsibility as developers to give you a product worthy of your money. Depends. You attacked. Please re-read your original post and see if you can notice the attack. Ok this one confused me. Yeah, PMDG have good products. Excellent systems modelling. My point remains the same. They have a team of 8 people working on the 737. They have been around for over 10 years. They promised a 737 in Mid 2010. They are 1 year late. All those developers on 1 project and they are 1 year late. The CRJ has 3 developers and Javier has been here for only 3 years. See the difference? What does this have to do with the CRJ and late releases?? No one is forcing you to stay here and refresh the forums 260 times an hour. Of course, you are more than welcome to keep checking, but you are waaaaay out of line when you think we OWE you something. You have paid no money. No one here owes you anything. Relax, be patient.

Then instead of hanging around these forums, how about you make some money and finish a contract project. We all want this CRJ. But how about this, PMDG said they would deliver their 737 in Mid 2010. They are STILL working on it. And that's a team of 8 people. THAT'S 1 YEAR LATE. And yes, I am saying you don't know how hard it is to make something like the CRJ. If I am wrong, please show me some of the add ons you have made for x plane. I would love to see them. EDIT: I didn't drop your karma. Sorry to disappoint you.

So when is your 747 coming out? It's not my forum, but this kind of attitude is uncalled for. If you get anywhere NEAR finishing something like a CRJ, then you'll see what's involved. Until then, read a good book and let these guys finish.

Couldn't resist.

I made a post in this thread last night but I was half asleep so I deleted it. Now I'm loaded up on caffeine and can post it again and have it make sense. The following is speaking for myself and Theo. Payware developers are sometimes under a lot of pressure as their work unfolds. Do we make it public to generate interest? No developer likes delaying a project. We don't do it to say "let's tease them some more and generate more interest." When we spend months/years on something, we definitely want it out so we can get started on the next project. We don't want to race anyone out the door with a product. It's not about being the first one out with an aircraft. It's about who can do their best work with an add on. If we find a bug, we want to fix it. If we fix 1 problem and cause 5 more in the process, this can cause MAJOR delays. But we would rather fix that 1 problem, then deal with those 5 more later if it means the aircraft can be more realistic and increase that level of immersion. Sometimes, it's those little things that put the shine on an already good product. As developers, we KNOW people want highly anticipated projects to be released. But however much someone wants a product released, the developer wants it released 50 times more. We don't mean to delay a project. And when we say soon, it kills us when we find a problem and it causes a delay. I sit there working with Theo and Cameron sometimes and when a series of problems presents itself, I say "Another delay...man, people are gonna be pissed." But nothing we can do. It's like driving to work and you get a flat tire. "Man, I'm gonna be late. The boss is gonna be pissed." Problems are inadvertently caused by the developer. ESPECIALLY programming. When there's custom code, there's going to be problems. But when we fix them, the result makes the aircraft that much more realistic and IS worth it. On the flip side, what if we say nothing. What if EVERY developer says nothing. Where's the anticipation? No work in progress renders. No statements. No timeline. It would be a very boring development world when we have nothing to look forward to. Perhaps better timeline management will fix the problem. Adding a 3-4 month buffer to an estimated release date. I think it would be much better to have the anticipation of an upcoming project by seeing screenshots of a work in progress.

We'll see what we can do. Shouldn't be a problem

The easy stuff is when I get down to 3 cups of coffee a day. I'm nearly there. I'm at 5. (Theo stressing me out daily counts as 1 coffee) You're welcome, Perry.

We honestly don't mind the comments. On the rare occasion, it can get a little too far. But this example was something we intended to fix anyway. I was in the mood to get it out of the way anyway so, seeing as Theo is in charge of displays and avionics, I got him to take care of it. 3 minutes later... Just keep in mind, if something looks wrong, there is a very high possibility that we know about it and intend on fixing it. The easier it is to fix, the later we plan on fixing it.

It's still a WIP. This is all a part of cleaning up the stuff that needs to be cleaned up. Just about everything works but we need to make sure it LOOKS right as well as working right.

That's a tough question. The vast majority of developers for x plane make freeware and they may not be able to afford a programmer. And obviously they only do it as a hobby. If you would like to take up some pro-bono work (free), I'm sure many developers would like to see what you can do. As for payware, depending on the developer, you might have to prove yourself with some previous work. The market isn't quite there yet for a giant team of developers working under the one flag on one project, but it is growing very rapidly. It's definitely possible to make a living with programming for a developer but it's not easy. What I would suggest is downloading a freeware aircraft, coding some kind of system in it and make it available for download (with the original developers permission). If it's something that impresses some developers, it would be a foot in the door and a step on the right path. Spend a major part of your time working your craft and perfecting as much as you can. You're definitely well on your way seeing as you have some background in programming. Now you just have to get yourself noticed with an example of some x plane work.

If you want to code using the officially supported SDK, learn C/C++ You can also learn LUA and code using Ben Russell's utility, "Gizmo". He offers support in these forums.

Standard procedure is to flare the aircraft by pitching up 5-6° from approach attitude when the landing gear is a few feet above the ground. When initiating the flare, gently reduce power to FLIGHT IDLE. Immediately after touchdown, reduce the power levers to GROUND IDLE. Two annunciators on the Flight Status panel will come on when you are in Ground Idle. Rest assured, this is all in the documentation I'm providing in the "Charts and Procedures" section. No previews yet, though. I'm doing a 4th revision which involves adding a description of something I added last week. But the above is standard procedure.

Theo isn't around today, but I'm sure I speak for him when I say thank you for your appreciation. As Theo's cartoon depicts, we really do stay cooped up for months. Although the documentation has kept me from sounding like a caveman and I still use the toilet on a regular basis. The facial hair is there, though. I DO check the forums on a regular basis. The comments make me smile in an otherwise stressful environment (typing manuals and fixing them 4 times over while having a very rambunctious 5 year old call out "Daddy" every 10-15 minutes). The Saab would be nowhere near what it is now were it not for Cameron and Ben. Gizmo has been the best decision I have ever made. I was very hesitant at first but I trust Cameron and Ben more than enough to have faith in what Gizmo can do. So far, it has far exceeded my expectations. The things I have seen being done with it absolutely astounds me. I don't think people truly understand how powerful it really is. That's why I would like to extend YOUR thanks to Cameron and Ben. I know I keep saying the Saab will be finished "soon" and it kills me when that "soon" appears never-ending. The last few days have been filled with constant testing and documentation revision. All I can tell you is we are working very long hours to make sure everything is done properly. And yes, it will be "soon". The bright side to all this waiting? We can use the src code of the Saab coding for all our future products (making small adjustments and additions to the code to fit the aircraft) so everything will take a LOT less time. And we have some juicy aircraft waiting to be finished, including the 747's and the Hawker 4000.

Carbin (The person who has twice quoted kesomir with his own spam links) I am getting a little tired of deleting your spam posts. If you want to quote someone else, then it's no problem. If you quote someone again with spam links to Apple products that were NOT in the original posters forum post, you will be banned. Have a nice day.

Tell me about it!? Even my daughter is asking "When are you going to finish your Saab?". And she's 5. I'll be providing 2 tutorials on how to fly it. One will be a quick flight without going through the whole start up procedure and the other one will be a full tutorial from start up to shut down with a bunch of navigation stuff in between. It'll make it easier to get through everything. (God help me, I'm proof reading my posts before submitting them!? I need a vacation.) :-\

Let's not get hostile, gentlemen. I have been going over the 3rd revision of the documentation to make sure everything is formatted properly and the info is sufficient. The actual aircraft is still being worked on. Took it for a few tests over the last few days, and so far, some figures are damn close with others being spot on accurate. There are a few more things to do with a couple of systems and on-screen annunciators with the autopilot modes. As soon as the manuals are finalized, I'll put them up. Believe me, there is quite a bit to study.

If only I studied this much in High School. I would have finished in the top 2%.

I suggest you contact X-Plane support. That would be your best bet. Start with this... http://x-plane.com/pg_support.html

When people feel threatened by the competition, they try to silence the competition in any way they can. The "cheating" scandal was an excuse to ban you. I think we all know the real reason you were banned. Javier, the CRJ will be the standard developers should rise to. You deserve the best out of it and I sincerely wish you great success with it.

Thanks Much appreciated!