Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/24/2012 in all areas

  1. Wait, where did I watch a hydraulics system demo video recently? I was already looking forward to that airliner project and now that I know you're involved I'm even more excited and more than willing to forgive the delay on the moo. But I think it would be good not to spark hopes for a "early" moo update any more - until you're REALLY done with it. After weeks and month of delay it´s a little bit annoying to read "with any luck, it won't take as long as I might think and I could just go...."hrm...that works" and put something out." We all should drop that release-talk for now and relax. Cheers Flo
    1 point
  2. well thank you Simon...I'm happy you feel that way. I have no issue with the ribbing I get. Customers should be demanding and I did seem to just "fall out a bit". I did; however, say I'd elaborate a bit more once the xplane dev conference is over and that's exactly what I'll do. The primary reason for the MU-2 delay that I haven't said is that I have diverted to work on a prominent airliner project in addition to a scenery project and of course, laminar work. I'm a developer on said airliner team with a demanding workload....having recently wrapped up a hydraulics simulation *cough *cough. Internal situations on this project towards Dec/Jan caused me to expedite my work and the MU-2 moved to the back-burner. I'm also putting my scenery experience with XP10 to good use with another talented 3D developer to put out a "designed for V10" scenery product and not just a modified conversion. The fact that the code I used 3 years ago on the MU2 doesn't work as well with XP10 features I have available to me now that I did not then doesn't help. If the Moo was the only project I was working on, sure I'd be making progress, but at the end of the day, I'd have a marginally known aircraft with a free update and little cash in my pocket. I found it imperative, in order to stay in this market and continue to make good add-ons, to basically pause the work and sprint to some more profitable add-ons during this critical time when MSFS users would start looking our way. Discussion from the conference shows that was a good decision. I showed our work to some folks at the x-plane dev conference and several PMDG owners indicated we very easily kept pace. The work done on this project will find it's way back into the MU2 and the code base for the electrical system will allow "per circuit breaker" simulation on the MU2.....not sure I'll do that, but it can. Also, I've learned quite a bit more during this dev process that should allow me to pretty much perfect the MU2's operation. I probably will hold off on MU2 work until the scenery comes out though as that should be out first and give me some breathing room. With no add-ons for a while and part-time laminar work....money ain't exactly knocking on my doorstep.....yet I feel this is the prudent move as once this work is done later this year, I will be in a position to continue to develop higher quality add-ons for x-plane. It's a very promising time for XP and by the end of 2012, we (at Laminar) hope to incorporate some nice things that will endear XP to more MSFS users. So that's what's up. I work 10-12 hours between laminar, the airliner and the scenery....and well, the MU2 gets leftover hours depending on my mood. It was only recently though that I identified some V10 issues that finally made me say, "OK, I have to back up a bit on my code" and on a day or two, here and there, that is exactly what I'll do and with any luck, it won't take as long as I might think and I could just go...."hrm...that works" and put something out. But for now, I find it imperative to work on the airliner and some custom scenery. So if nothing else...the MU2 waits a bit, but the time is not wasted on things that won't benefit end users. I'll keep reporting as usual when work gets done, even if its not visible. Tom K
    1 point
×
×
  • Create New...