Darn, the PMDG Jetstream 4100 is not on the list (yet) for Xplane10 !

It's not even in P3D yet, which is a relatively minor port job compared to Xplane!

All of these claims are wrong!

 

- FLCH does work just like the real one and we have not had one single complaint on it by the loads of 737 real pilots that have tried it for over 1000 hrs of block time.

- Autobrake, which I personally gave Austin the documentation on is 737 values.

- We have a 100% custom engine model which is most likely the most accurate jet-model ever made in ANY sim in terms of thrust and drag at all altitudes, mach and temperatures.

 

The FMC is still missing a few functions as we stated long before release, but will be implemented.  And yes, we had our share of bugs - like everyone else.

Im not trying to be a pain...  Really.   But what you are telling me is the exact opposite of what Jan on the xpilot forums has wrote in response to my and others threads.  He has stated that the autobrake is based on the default xplane model.  FL Change dives at 6000fpm, and overshoots mcp speed when engaged from cruise altitude, even with the aircraft already at target speed before engagement.  Many others on the xpilot forum have confirmed this.  And regarding the engine model, this has also been confirmed by Jan, that the egt, oil pressure, and oil temperature are not yet custom coded.  The egt should not be 400 degrees at cruise, it should be between 600-700, fuel flow should not be zero when the engines are idling at the start of descent, and oil temperature should not immediately drop to zero when the throttles are brought to idle at descent,  these things have been confirmed by other IXEG developers so I'm not sure what the discrepancy is.  Don't get me wrong, the aircraft has many great points, the best looking visual model for xplane imo, spectacular night lighting, great soundset, and most other systems seem to be modelled very well, but its still missing alot.  And whether or not different people like the fmc, or choose not to use it, or think real pilots don't use vnav etc. they are missing the point, it is part of the plane and its missing quite a bit at the moment.

 

 

is based on the default xplane model

 

And the default X-Plane model is for a 737.

 

Did you see Jan's previous post?

 

I can't comment on your other points.

 

 

Im not trying to be a pain...  Really

 

No problem, but there is a big difference between "bugs", "not modelled right" and "not modelled yet".  So please try to keep them apart 

On the IXEG autobrake being too mellow:

 

I tested the autobrake at setting "2":

 

IXEG: 1.44 m/s²   Real 737: 1.52m/s²

 

This is a 5.5% difference, certainly not the demise of the western civilization as some people claim :smile: .

 

Jan

Burn the witch

 

I cannot enjoy my flightsim experience with such an inaccurate decelleration modelling shown here.

it is part of the plane and its missing quite a bit at the moment.

 

 

As are many modern software products,  I'm not saying that you are not speaking the truth on several things, I am just saying that IXEG is not unique in these issues....for example:

 

We have fixed the following:

• Reduced numerous CTDs related to terminal procedures in the navdata.

• Fixes for several situations that could result in an incorrectly calculated VNAV path. 

• RTE page now automatically picks the correct waypoint when an airway is entered in the VIA column and the waypoint entered in the adjacent TO column has duplicates in the navdata that are not on the airway. 

• Fixes for several situations that could result in a crash message.

• Fixes for several scenarios that could result in a CTD while performing a go-around. 

• Fixed a CTD caused by entering a value higher than 100 into the cabin lights.

• Autobrake system completely redone, values match Boeing braking distance tables extremely closely. 

• Added the ability to make and use custom runway-based waypoints 

• Tweaked approach idle values to be more accurate 

​OH WAIT....this is not stuff IXEG fixed, its about 10% of PMDGs Service Pack 1 update log (and 2 and 3 is equally as long).   ...and just like PMDG, we will continue to improve and update the product.  This is the way of software development and though the elements of the things "to go" differ between products, all modern released software products have such a list and its always a ways to go to shorten it.

 

-tkyler 

I think the IXEG guys have done an amazing job with the 737 and in one fell swoop have raised the bar for X-Plane. It's still not 100% complete or indeed perfect but is anything in life?

 

In terms of the 777, RSR was pretty clear in his recent update. He said in the 'none too distant future' you could expect the entire PMDG line to be ported into X-Plane. None too distant in anyone's book sounds more like months/a couple of years rather than years/decades!

tkyler ,

 

"We have fixed the following:" ...

All good news, thanks for sharing it.

 

Do you have a list of current "bugs" that are being fixed now and info on items that are not modeled yet but are to be included at a later date?

tkyler ,

 

"We have fixed the following:" ...

All good news, thanks for sharing it.

 

Do you have a list of current "bugs" that are being fixed now and info on items that are not modeled yet but are to be included at a later date?

 

Please read Toms post again. More slowly. Word for word.

"Please read Toms post again."

I assume you mean "-tkyler" , if so,  I did not previously know he was Tom ... sorry about that.

 

 

I was asking about what is currently being fixed .. e.g., not in his list.

 

And features that are not currently modeled but will be added later (also not in his list) ?

And again - the list he posted has nothing to do with IXEG - try one more time. Hint: Focus on what he wrote AFTER the list... :wink:

 

Jan

 

 

Im not trying to be a pain... Really. But what you are telling me is the exact opposite of what Jan on the xpilot forums has wrote in response to my and others threads. He has stated that the autobrake is based on the default xplane model. FL Change dives at 6000fpm, and overshoots mcp speed when engaged from cruise altitude, even with the aircraft already at target speed before engagement. Many others on the xpilot forum have confirmed this. And regarding the engine model, this has also been confirmed by Jan, that the egt, oil pressure, and oil temperature are not yet custom coded. The egt should not be 400 degrees at cruise, it should be between 600-700, fuel flow should not be zero when the engines are idling at the start of descent, and oil temperature should not immediately drop to zero when the throttles are brought to idle at descent, these things have been confirmed by other IXEG developers so I'm not sure what the discrepancy is. Don't get me wrong, the aircraft has many great points, the best looking visual model for xplane imo, spectacular night lighting, great soundset, and most other systems seem to be modelled very well, but its still missing alot. And whether or not different people like the fmc, or choose not to use it, or think real pilots don't use vnav etc. they are missing the point, it is part of the plane and its missing quite a bit at the moment.

 

Jan,

 

Ok, Sorry about that ... I thought his list was in regards to the post I quoted here and he quoted from  .. which was about IXEG.

But no it is about PMDG ..... and their problems and fixes / issues.

Sorry, my fault in not reading properly.

 

 

So, this would be the wrong forum area to ask about IXEG 737 ... which is what I was actually interested in but was not specific.

 

Do you have a list of current "bugs" that are being fixed now and info on items that are not modeled yet but are to be included at a later date?

http://forums.x-pilot.com/forums/forum/183-general-discussion/

 

M

M,

 

Do I need to read many posts and figure it out or are there current lists of :

current "bugs" that are being fixed now and info on items that are not modeled yet but are to be included at a later date?

 

Maybe you have a direct link to the info?

M,

 

Do I need to read many posts and figure it out or are there current lists of :

current "bugs" that are being fixed now and info on items that are not modeled yet but are to be included at a later date?

 

Maybe you have a direct link to the info?

 

 

There is no such a list, in fact it seems not to be a common practice having a public list because things/priorities may change during coding.

 

You have to be active on the forums to have an idea what was reported, what seems to be already fixed for upcoming update, whats seems to take longer, etc.

 

The official list is only provided when the update arrives, named changelog.

 

 

EDIT: this link is not a list at all but the starting point to understand what is going on. You still have to read threads.

http://forums.x-pilot.com/forums/forum/202-bug-reports/