Goran_M

That's the main gear done.

I spend my days on my day project. This is my night project. Theo's going to hate me.

I'll leave that opinion up to the reviewers and customers.

Ooh yeah guys! Love that seat already. But God, are all those dc3 interiors that phlegm-green? I really hope not. Would keep the pilots awake I suppose. Wait til you see what other textures we plan on adding. All based on real DC-3's

Theo is getting very eager to texture this one. I've paid for some high resolution texture sets a few days ago and Theo is very happy with how they look. Here's a little sample of the cabin seat.

Thx for the feedback, guys. I'm juggling a couple of projects atm but this one shouldn't take long at all.

For the last couple of months, my work on the Saab has been mostly organising various areas, acting as consultant to Cameron (for programming) and typing up the documentation. The documentation is just about done but I need a 100% working version of the Saab so I can finish it and Cameron is continuing that side of things. So in between that and a couple of other things I have going, I have continued work on the DC-3 and this serves as a formal announcement that this will be the next project Theo and I will continue with while the Saab is being finished. With that, here are the first few screenshots: (I know of the mesh issues. As usual, all will be fixed) EDIT: Uploaded to Flickr.

More coding and we're giving way to the CRJ EXPRESS.

You may have "Autorun" turned off. If this is the case, go into your Windows Explorer, select the Disc Drive, find the X Plane executable file and double click it. I know you said you got a new x plane disc, but check the disc anyway for scratches, dirt, smudges, etc... You may also have dirt or dust inside the disc drive. Give it a good blow inside the drive or even better, get a can of compressed air and use that.

I'm used to modelling close up and working on 1 gauge at a time. Looking at it from that perspective makes me want to start consuming copious amounts of alcohol.

Decisions have been made. I'll be posting something very soon with regards to the Saab and the next side project.

If all else fails, delete preferences.

Pixel shaders hit the framerates pretty hard. if it was up to me, I would get rid of the pixel shaders if the fps were getting hit. I prefer to have anti aliasing so I can read the displays. 512MB card should be fine. We have a few test rigs we're trying it on and everything looks good.

Sent you an email.

Jeff, we all love Ben. He's full of character. I can tell you that I have gotten feedback from a select few people and they have given me very positive feedback on the Saab. In appearance, flight model, systems modelling and performance. However, it's very different to the CRJ (obviously) in many ways. In any case, we're confident people will enjoy it. The manuals will be available to download soon and you'll get to see everything that's in it. It's testament to how powerful Gizmo really is. And we're still only scratching the surface.

Wow, thanks. I sure hope the Saab lives up to expectations. We've had some great feedback so far.

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.