Jump to content

IXEG 737 Progress Update - March 12th


tkyler
 Share

Recommended Posts

3 hours ago, jimbim said:

Hello Jojo,

You could use FlyWithLua and write a little script to read the axis. Then you can define ranges and trigger the correct flap position fitting to your range.

Should be pretty easy.

 

Greetings,

Sebastian

 

i am interested on this as well. I do have a goflight tqm6adv and do not use the flap lever because xplane does not support flap levers natively and sometimes they do not even fully close inflight and you rip them.

but having a lua script to define ranges will surely make them work.

can you provide us a script example to tune from as a starting point? thanks!

Link to comment
Share on other sites

hmm I don´t know if it might be that simple, because for years back I also had a GoFlight Throttle Quadrant and know it was not plug and play as you say.. Windows only see the device but windows can´t communicate whit the hardware to calibrate it´s axis.. and If it is still that way you cant assign the axis inside x-plane directly like other plug and play devices.. only by there software that runs like a plug-in..

Then you have to know if the driver from GoFlight uses the default axis or direct input by dataref for the commands it sends out to the simulator.. this can cause a problem if it sends direct dataref input to flaps and such.. Because if this plane make use of custom codes for those things we have to know them instead to make it work but then you can only use this code for this specific aircraft and not create a general file that can be used by other values for other aircraft’s if that might be handy.. But also what input range does it use for the axis is it from -16084 to 16084 or is it like x-plane default from 0 to 1..

Not that I think you cant do it as I think you can but you have to know quite some things about it.. and sadly I don´t have my device so I could try create something that you could use..   

But we are off topic here and think you might start a chat about it over at the FlyWithLua support forum.. Not that I don´t want to talk about it!

Link to comment
Share on other sites

4 hours ago, jimbim said:

Hello Jojo,

You could use FlyWithLua and write a little script to read the axis. Then you can define ranges and trigger the correct flap position fitting to your range.

Should be pretty easy.

 

Greetings,

Sebastian

Thanks for the info Sebastian, I will take a look at it and try to come up with some very basic tool then.

Link to comment
Share on other sites

16 minutes ago, KAPTEJNLN said:

hmm I don´t know if it might be that simple, because for years back I also had a GoFlight Throttle Quadrant and know it was not plug and play as you say.. Windows only see the device but windows can´t communicate whit the hardware to calibrate it´s axis.. and If it is still that way you cant assign the axis inside x-plane directly like other plug and play devices.. only by there software that runs like a plug-in..

Then you have to know if the driver from GoFlight uses the default axis or direct input by dataref for the commands it sends out to the simulator.. this can cause a problem if it sends direct dataref input to flaps and such.. Because if this plane make use of custom codes for those things we have to know them instead to make it work but then you can only use this code for this specific aircraft and not create a general file that can be used by other values for other aircraft’s if that might be handy.. But also what input range does it use for the axis is it from -16084 to 16084 or is it like x-plane default from 0 to 1..

Not that I think you cant do it as I think you can but you have to know quite some things about it.. and sadly I don´t have my device so I could try create something that you could use..   

But we are off topic here and think you might start a chat about it over at the FlyWithLua support forum.. Not that I don´t want to talk about it!

I do not have installed any driver. I go to xplane joystick and assignments and set left throttle lever to throttle1 and right lever to throttle2 and they work flawlessly in all my payware birds (ff757/767/777, fjs727/737, rotate md80, saab340 and awaiting for the ixeg 737CL :))

For the reverse handles i assigned them to xplane max reverse thrust hold. i can not control how much reverse but they work flawlessly and feels great pulling those levers after landing.

I tried assigning the flaps lever to flaps also, and they do work. But as jojo3800 said, the xplane flap lever dataref goes 0.0 to 1.0 and you get crazy flaps settings like 13.2, 14.8 and whatever in between. The goflight tqm has a physical detent for flap settings. if could set ranges for the dataref it should work

biggest problem is when closing the lever to 0, sometimes the dataref it is still 0.0001% and you rip the flaps inflight. 

Link to comment
Share on other sites

Okay fine that is good news for the new device but I still say go to FlyWithLua support forum and talk about it there.. there might be someone that can help.. as yes I know 0 to 1 is a bit pain full as it is a small range.. but hardware output is 1 thing and another is the simulator (0 <-> 1)

Edited by KAPTEJNLN
  • Upvote 1
Link to comment
Share on other sites

I think i am waiting for a plane that doesn't exists... Always same escuses like "few things to be solved", "Gizmo crashes" and so on for 3-4 months. This is not a correct behavior, you should work instead of post screenshots. Altough  It will be a great add on, but i hope that it will be for XP10 and not for XP256461

  • Upvote 1
  • Downvote 7
Link to comment
Share on other sites

2 minutes ago, tolix said:

I think i am waiting for a plane that doesn't exists... Always same escuses like "few things to be solved", "Gizmo crashes" and so on for 3-4 months. This is not a correct behavior, you should work instead of post screenshots. Altough  It will be a great add on, but i hope that it will be for XP10 and not for XP256461

It should be noted that when Tom says "Gizmo Crashes" what he actually means is that "My Lua scripts made gizmo display an error message bout my bugs."

Gizmo is NOT crashing to desktop. It is merely showing Tom the location of his bug.

 

A subtle point but one that would enormously affect the quality of the end product if Gizmo was "crashing". It doesn't.

  • Upvote 1
Link to comment
Share on other sites

36 minutes ago, tolix said:

I think i am waiting for a plane that doesn't exists... Always same escuses like "few things to be solved", "Gizmo crashes" and so on for 3-4 months. This is not a correct behavior, you should work instead of post screenshots. Altough  It will be a great add on, but i hope that it will be for XP10 and not for XP256461

Dude, there are videos about this plane, pictures, and major updates that show progress. Plus, why would someone waste 5 years of their time and money? 

 

I'm sorry, but you don't know what it's like to create a plane with such detail ixeg is doing. If you looked back, you would see that Tyler has been working very hard on the fmc. The plane is coming, it'll be here when ready. 

Link to comment
Share on other sites

38 minutes ago, poodster said:

Dude, there are videos about this plane, pictures, and major updates that show progress. Plus, why would someone waste 5 years of their time and money? 

 

I'm sorry, but you don't know what it's like to create a plane with such detail ixeg is doing. If you looked back, you would see that Tyler has been working very hard on the fmc. The plane is coming, it'll be here when ready. 

it was ironic. I only think that 5 years are too much, also for a perfect plane. I know what it takes to develop a perfect plane, just beacause i am doing it. The most is fmc programming, but it request a specialist and this is what i needed for my plane, until i decided to develop a citation. "The plane is coming" I am sure about that, sure and faithful to the developers, but they shouldn't give us "release dates" like in the end of december... This is my only critic

  • Upvote 1
  • Downvote 2
Link to comment
Share on other sites

Just wanted to let you know that I (and probably most of the other people waiting here as well) would highly appreciate a "full flight preview" of the 733 by Jan. It doesn't need to be edited since we all don't want you to spend too much time on the video instead of hunting down nasty bugs :D.

Link to comment
Share on other sites

32 minutes ago, tolix said:

it was ironic. I only think that 5 years are too much, also for a perfect plane. I know what it takes to develop a perfect plane, just beacause i am doing it. The most is fmc programming, but it request a specialist and this is what i needed for my plane, until i decided to develop a citation. "The plane is coming" I am sure about that, sure and faithful to the developers, but they shouldn't give us "release dates" like in the end of december... This is my only critic

If you read back, you will see Tkyler explain what you want. His quote at the end of his comment is "wouldn't it be great to have this plane is 5-6 weeks?" 

 

You will understand what that means if you go back and read it. Also, you should know that these guys were doing this project on their spare time. 5 years may seem a lot, but with what we have seen, we can see why it takes this long with the circumstances. 

  • Upvote 2
Link to comment
Share on other sites

1 hour ago, tolix said:

I only think that 5 years are too much, also for a perfect plane. I know what it takes to develop a perfect plane, just beacause i am doing it.

I look forward to seeing your perfect plane on the market sometime before 2021, although you might want to work on your people skills if you want to make any money from it.

  • Upvote 2
Link to comment
Share on other sites

IXEG, how 'sound-wise' w.r.t the related systems is this aircraft modeled? An example: it ever surprised me with the PMDG 777 that the PACK sound volume diminishes a little bit when you operate the flaps since they require power (situation: engines off, apu on and corresponding systems on in order to operate the flaps obviously). At this moment, I really got a 'WOW!!' feeling and hence hope IXEG has the same 'sound-wise' detail.

Link to comment
Share on other sites

35 minutes ago, FSSteven said:

IXEG, how 'sound-wise' w.r.t the related systems is this aircraft modeled? An example: it ever surprised me with the PMDG 777 that the PACK sound volume diminishes a little bit when you operate the flaps since they require power (situation: engines off, apu on and corresponding systems on in order to operate the flaps obviously). At this moment, I really got a 'WOW!!' feeling and hence hope IXEG has the same 'sound-wise' detail.

 

Hi,

You can watch the movies we did (I mention and show the effect of airflow sounds changing on a few occasions, iirc.) to see how we modulate cockpit sounds.

Since the 737 has no pneumatically driven "demand pumps", driving the flaps in the same situation will not have an audible effect, though. You would see a spike in EGT - as the electrically driven hydraulic pump B has to struggle to satisfy hydraulic power demand, and therefore the APU has to generate more electricity. At the same time you could see a marked drop in hyd B pressure - with flaps driving a lot slower than on EDPs.

Cheers, Jan

 

Edited by Litjan
  • Upvote 8
Link to comment
Share on other sites

1 hour ago, FSSteven said:

IXEG, how 'sound-wise' w.r.t the related systems is this aircraft modeled? An example: it ever surprised me with the PMDG 777 that the PACK sound volume diminishes a little bit when you operate the flaps since they require power (situation: engines off, apu on and corresponding systems on in order to operate the flaps obviously). At this moment, I really got a 'WOW!!' feeling and hence hope IXEG has the same 'sound-wise' detail.

It is not lost on use to simulate every little "effect" due to every possible input by every possible system, but the thing here is simply the "volume" of things to be dealt with.  Being this is our first product, in order to be competitive, we really have to achieve the same technical level as a 17+ year old company with more resources and experience and well....that is just taking a while, especially given that we're a 4 man team working in our spare time.  This is a testament to using Gizmo and its vastly reduced compilation time.  It is our belief; however, that once we get this initial tech on the market, we can then expand upon the smaller details and try and capture as much of the real thing as possible.  Rome wasn't build in a day, nor in 5 years.  In time, we'll refine the 737 and eventually, get to that vision we have.   Its enough for now just to get a really robust FMS / AP implementation, which is priority 1.

-tkyler

  • Upvote 7
Link to comment
Share on other sites

On March 14, 2016 at 9:05 AM, Morten said:

I never get tired of looking at XP's lighting.  It's just so realistic! Not sure if I counted them correct, but the 737 has about 18 (!) different lightsources inside the cockpit that you individually can adjust to your liking.  Great way to waist time during a long cruise at night :)

 

Light.jpg

Truly buetiful picture, and I don't no about you guys, but I CANT &*^%$# WAIT!!!!!  Great work IXEG.

  • Upvote 1
Link to comment
Share on other sites

On 14 de marzo de 2016 at 10:05 AM, Morten said:

I never get tired of looking at XP's lighting.  It's just so realistic! Not sure if I counted them correct, but the 737 has about 18 (!) different lightsources inside the cockpit that you individually can adjust to your liking.  Great way to waist time during a long cruise at night :)

 

 

ohh men this aircraft is going to be amazing. hopefully it gets released soon, i have been awaiting patiently but it is starting to get difficult... :) 

Link to comment
Share on other sites

IXEG Team:

I am a customer of "Brand P" and one of the biggest values they bring is they high level of quality of their software.  Please help set a new standard among X-Plane dev teams and release a great product, a "v1.0" can stand alone and not *have to have* updates.

As far as comments about dev time:

I've been part of software dev teams and it's always easy when you start and gets harder as you go, especially when it's "close".  I remember reading comments on our product's forum about delays, guesses on what we did all day and worse.  It can be demoralizing and while some devs develop a thick skin, it's tough to read or see.

Imagine - your mom is making cookies for you.  You go into the kitchen, complain when can't help taste the dough and you want to take them out of the oven early.  When your mom doesn't let you, you start questioning her ability to bake, her skills in measuring ingredients and in some cases, her quality as a parent.  How would she feel?

Happy to wait for a product IXEG is proud to sell...

Steve

  • Upvote 2
Link to comment
Share on other sites

1 hour ago, stevekirks said:

IXEG Team:

I am a customer of "Brand P" and one of the biggest values they bring is they high level of quality of their software.  Please help set a new standard among X-Plane dev teams and release a great product, a "v1.0" can stand alone and not *have to have* updates.

As far as comments about dev time:

I've been part of software dev teams and it's always easy when you start and gets harder as you go, especially when it's "close".  I remember reading comments on our product's forum about delays, guesses on what we did all day and worse.  It can be demoralizing and while some devs develop a thick skin, it's tough to read or see.

Imagine - your mom is making cookies for you.  You go into the kitchen, complain when can't help taste the dough and you want to take them out of the oven early.  When your mom doesn't let you, you start questioning her ability to bake, her skills in measuring ingredients and in some cases, her quality as a parent.  How would she feel?

Happy to wait for a product IXEG is proud to sell...

Steve

Jeez, it seems to always be one extreme or the other. Either it needs to be released now or they should work on it for the rest of their lives. I am a part of a software dev team, as you put it, and I can confirm that the work gets harder to do as you get closer to release. I also can say definitively that release is always after the time you originally thought it was going to be. I also know from experience that, if you want to make it completely up to your standards with no issues, it will never be released. Your standards will continue to rise as your skill level does. At some point you've got to compromise. You've got to decide to release the aircraft and to improve the aircraft as you build skills. Nobody in this world is ever the best possible at anything. If you can do everything perfectly, you can do it faster. If you can do it perfectly and fast, you can do it more cheaply. There will always be room to improve. I really wish people would develop a more moderate stance on this. At some point products need to be released. "Very soon," (not quoting anyone here, just in general) turns to, "A few days," that turns to, "A few weeks," that turns into, "A few months." And it goes on and on until you decide, "You know what? This plane is way better than I ever expected. I'm going to release it now, and I can always update it afterwards." And, at this time, I don't *think* that this applies to the IXEG team. The time left before release seems to be dwindling now, as opposed to increasing. Sorry for this wall of text, I just had to get it out.

 

-VETTE

 

PS: Really looking forwards to release, however soon it may be. Now it's time to go make some money :P 

  • Upvote 6
Link to comment
Share on other sites

16 hours ago, tkyler said:

It is not lost on use to simulate every little "effect" due to every possible input by every possible system, but the thing here is simply the "volume" of things to be dealt with.  Being this is our first product, in order to be competitive, we really have to achieve the same technical level as a 17+ year old company with more resources and experience and well....that is just taking a while, especially given that we're a 4 man team working in our spare time.  This is a testament to using Gizmo and its vastly reduced compilation time.  It is our belief; however, that once we get this initial tech on the market, we can then expand upon the smaller details and try and capture as much of the real thing as possible.  Rome wasn't build in a day, nor in 5 years.  In time, we'll refine the 737 and eventually, get to that vision we have.   Its enough for now just to get a really robust FMS / AP implementation, which is priority 1.

 

Looking forward to your upcoming release! I do have a quick question.

Have you guys been able to expose a lot of datarefs and commands for the plane? I love to play around with external screens (like Air Manager) and build hardware cockpit panels. Sometimes getting all the data we need can be tricky. Are you guys exposing everything we need to create external panels, and reproduce the output of all glass screens, including the FMS, on external panels?

I warn you, I'll be one of the first guys trying to dig these up after you release!

Good luck on your launch, I know lots of people are looking forward to this plane!

  • Upvote 1
Link to comment
Share on other sites

we certainly want to encourage that kind of 3rd party interaction with the 737 and do plan to publish datarefs/commands as needed.  We are wanting to start a dedicated forum just for "interfacing geeks", where cockpit builders and other developers can discuss how to go about doing things and what is needed from IXEG to facilitate such efforts.

-tkyler

Edited by tkyler
  • Upvote 8
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...