MV22B Rel1.0 released

[rcbarend]

First, I have not yet managed to get the MV-22 towed. I press the TOW button on the refuel gauge, it asks me to set the throttle to 1/3, which I do. It releases the parking brake, but then it doesn't move. Neither fore nor aft. Regardless of throttle or stick position. Am I doing something wrong here?

Stick position has no influence, only throttle position.
A few questions:
- Are you using the panel.cfg I included in addon V4 ?
- If you move your throttle around the 1/3 position after the ParkingBrakes are auto-released, does the indicator changes from a green TOW to green PUSH, and back ?
- Which FS version are you using ? (Gold/Accel, Steam or P3D V??)

Second, and I don't know if this has been an issue anywhere else, the aircraft starts to shake and then to pitch and roll while shaking when I get into the hover below about 100 ft. Above that it seems to work normal. It appears to me as if it has some link to the ground effect. The shaking renders the aircraft nearly uncontrollable and can usually only be resolved in lowering the necelles, adding power and speeding up - which in turn doesn't really support a landing. Any ideas?

Yes, this is simulating the groundeffect, but for some reason this "jitter" appearantly works too strong on your PC. Not sure why, since I didn't change anything there.
- Did this also happen with addon V3 and/or with the Original MV22B package without my addon ??

By the way, you can remove this groundeffect by disabling the gauge:
//gauge02=rcb-gauges!VSTOL_Jitter, 0,0 (add the //)
in the VCockpit00 section of the panel.cfg.
But I'd like to find out why this effect appears to work so much stronger on your PC then for other people.

Rob

[kalong]

Hi Pat, Mark (and Maryadi, if you read this)

NOW I understand what you mean with "uncommanded roll" .
Yes, I have the same problem, but I never noticed it.

Just describing it for normal flight (nacelles 0), flying with fuel only in the main Left/Right tanks, no wind and leveled flight at 5000 ft and 220 Knots IAS:
With no stick or rudder input, the V22 very slowly starts rolling (banking) to the left (1 degree per 5 sec or so).

But I notice this depends strongly on how your set your Flight Model Realism sliders.
I allways fly with all five Realism slider fully right (Realistic).
But if I set the Torque slider to Easy (fully left), the problem is gone on my PC (FSX-Accel)
Can you confirm this ???

WHY the Torque realisme setting influences this: I don't have a clue.
IMO it shouldn't, since the proprotors rotate in reverse direction, with equal engines thrust and equal proppitch for both engines.

Maybe Maryadi can explain this ....

Rob

I can't get "uncomanded roll" to make a test.
so please make test for me

replace [flight_tuning] with this:

[flight_tuning]
cruise_lift_scalar     = 1.0
parasite_drag_scalar   = 1.0
induced_drag_scalar    = 1.0
elevator_effectiveness = 1.0
aileron_effectiveness  = 1.0
rudder_effectiveness   = 1.0
pitch_stability        = 1.0
roll_stability         = 1.0
yaw_stability          = 1.0
elevator_trim_effectiveness = 1.0
aileron_trim_effectiveness  = 0.0                //1.0
rudder_trim_effectiveness   = 1.0
p_factor_on_yaw                = 0.0
torque_on_roll                 = 0.0
gyro_precession_on_yaw        = 0.0
gyro_precession_on_pitch     = 0.0

[freded]

Pat,

I have yet another problem!

Am not able to show the list of objects for the sling when hitting Shift-J. It used to work perfectly but no longer. Don't know what has gone wrong or where to start looking for the problem...

Mark

PS: I foolishly posted this on the FS-Developer forum and Rob was kind enough to point this out to me... duh!

[seawing]

Stick position has no influence, only throttle position.
A few questions:
- Are you using the panel.cfg I included in addon V4 ?
- If you move your throttle around the 1/3 position after the ParkingBrakes are auto-released, does the indicator changes from a green TOW to green PUSH, and back ?
- Which FS version are you using ? (Gold/Accel, Steam or P3D V??)



Yes, this is simulating the groundeffect, but for some reason this "jitter" appearantly works too strong on your PC. Not sure why, since I didn't change anything there.
- Did this also happen with addon V3 and/or with the Original MV22B package without my addon ??

By the way, you can remove this groundeffect by disabling the gauge:
//gauge02=rcb-gauges!VSTOL_Jitter, 0,0 (add the //)
in the VCockpit00 section of the panel.cfg.
But I'd like to find out why this effect appears to work so much stronger on your PC then for other people.

Rob

Morning Rob,

- yes, I am using the pnael.cfg of V4.
- What I see when I engage TOW is the following. The "TOW" label is grey. When I hit it, it turns to flashing green until I move the throttle to 1/3, after which it turns red. There is no "PUSH" label.
- I am using FSX-A

In regards to the jitter, I believe it also happened in V3. It happens more often in a dense scenery, less on a ship at sea - but it still happens. My machine is quite old (i7-3770 @ 3,4 GHz with 8 GB RAM), so that might contribute.
What other infos could I provide you with to help iron out the problem?

Regards,

Seawing

[PhantomTweak]

Am not able to show the list of objects for the sling when hitting Shift-J. It used to work perfectly but no longer. Don't know what has gone wrong or where to start looking for the problem...

Ok Mark, may I presume you're still using the same AICarriers? You haven't changed the version, or the location of the folder it's in, or moved the conf.d folder out of it? Have you changed, or added to/subtracted from the EXE.XML file? Have you changed the .cfg file, either the main, or the one we added for the sling loads? Have you changed the size of your screen, when in the sim? Like gone to using full screen, or from that back to windowed? Do you see all 10 menu choices that should be there when you hit SHFT+J? They go from 1-0, top to bottom. Do you see them all? If not, did you scroll down until you did? On mine, with the original AiCarriers.cfg in the main AIC folder, and only the sling load .cfg in the conf.d, I have 3 pages to the SHFT+J menu, the first sling load being #9 on the first page. Can you see the #9 entry? Or the menu choice #0 at the bottom indicating the next page?
Now, I have to go, it's late...

Let me know
Pat☺

[freded]

Ok Mark, may I presume you're still using the same AICarriers? You haven't changed the version, or the location of the folder it's in, or moved the conf.d folder out of it? Have you changed, or added to/subtracted from the EXE.XML file? Have you changed the .cfg file, either the main, or the one we added for the sling loads? Have you changed the size of your screen, when in the sim? Like gone to using full screen, or from that back to windowed? Do you see all 10 menu choices that should be there when you hit SHFT+J? They go from 1-0, top to bottom. Do you see them all? If not, did you scroll down until you did? On mine, with the original AiCarriers.cfg in the main AIC folder, and only the sling load .cfg in the conf.d, I have 3 pages to the SHFT+J menu, the first sling load being #9 on the first page. Can you see the #9 entry? Or the menu choice #0 at the bottom indicating the next page?
Now, I have to go, it's late...

Let me know
Pat☺

Pat,

Same AICarriers.
Same version.
Same location: in FSX folder.
AICarriers contains: aicarriers.cfg, AICarriers.exe, readme.txt and folder conf.d, which contains: xpack.cfg.bak and Sling Loads for AICarriers.cfg.

Have not changed either .cfg files

Have not changed size of screen - always use windowed screen.

As I said: nothing appears when I hit Shift+J - no menu, just nothing...

Sling Loads for AICarriers.cfg:-

[base]throttle=60
menu_shortcut=shift+j
confdir=conf.d

[formation.0]
title=pallet_of_Boxes_sm plus other
unit.0=pallet_of_Boxes_sm, 0, -15
unit.1=Food_pallet , 0, 15
unit.2=pallet_of_Boxes_sm, 15, 0
unit.3=crated_cylinder_sm, -15, 0
unit.4=fuel_bladder_sm, 15, 15
unit.5=fuel_bladder_sm, 15, 13
unit.6=fuel_bladder_sm, 13, -15
unit.7=Stretcher_sm, -13, 13

[formation.1]
title=AC_Unit_sm
unit.0=AC_Unit_sm, 0, 15

[formation.2]
title=CableCar_Wheel_sm
unit.0=CableCar_Wheel_sm, 0, 15

[formation.3]
title=crated_cylinder_sm
unit.0=crated_cylinder_sm, 0, 15

[formation.4]
title=cratedfueltank_sm
unit.0=cratedfueltank_sm, 0, 15

[formation.5]
title=fuel_bladder_sm
unit.0=fuel_bladder_sm, 0, 15

[formation.6]
title=gas_bottles_sm
unit.0=gas_bottles_sm, 0, 15

[formation.7]
title=Generator_sm
unit.0=Generator_sm, 0, 15

[formation.8]
title=pallet_of_Boxes_sm
unit.0=pallet_of_Boxes_sm, 0, 15

[formation.9]
title=Propane_Tank_sm
unit.0=Propane_Tank_sm, 0, 15

[formation.10]
title=box_of_drums_sm
unit.0=box_of_drums_sm, 0, 15[B] "

[Formation.11]
title=Stretcher_sm
unit.0=Stretcher_sm, 0, 5

[Formation.12]
title=Food_pallet
unit.0=Food_pallet , 0, 15


I have changed nothing in and under AICarriers, which is why I am stumped (to use a cricket expression!).

The MV-22B is stationary on the ground with engines running in FSX.

Foder: FSX\SimObjects\Airplanes\MV-22B_Osprey\panel\panel.cfg contains: Window00=DOWN-CAMERA (FSX ONLY) // NEW
Window01=TRACK&REFUEL (FSX ONLY) // NEW
-both of which appear on screen when appropriate Shift+X is hit.

In Autopilot: Only buttons 'ON' are VOR/ILS and AUTO NAC. In Overhead: VRS is 'ON'.

Can you think of anything else I should check?

Hope you slept well!

Mark

[rcbarend]

I can't get "uncomanded roll" to make a test.
so please make test for me

replace [flight_tuning] with this:

[flight_tuning]
cruise_lift_scalar     = 1.0
parasite_drag_scalar   = 1.0
induced_drag_scalar    = 1.0
elevator_effectiveness = 1.0
aileron_effectiveness  = 1.0
rudder_effectiveness   = 1.0
pitch_stability        = 1.0
roll_stability         = 1.0
yaw_stability          = 1.0
elevator_trim_effectiveness = 1.0
aileron_trim_effectiveness  = 0.0                //1.0
rudder_trim_effectiveness   = 1.0
p_factor_on_yaw                = 0.0
torque_on_roll                 = 0.0
gyro_precession_on_yaw        = 0.0
gyro_precession_on_pitch     = 0.0

Hi Maryadi,

Yes, adding the last 4 lines solves it, so I don't get the "uncommanded roll" anymore even with full realisme for all sliders.
Not surprised though, since using 0.0 effectively disables any effect of these FDE features..

Appearantly another subtil difference (in FDE) between FSX-Accel/Steam (which we use) and P3D (your FS version).
Can Pat/Mark confirm that this also works for you ???

Rob

[rcbarend]

- What I see when I engage TOW is the following. The "TOW" label is grey. When I hit it, it turns to flashing green until I move the throttle to 1/3, after which it turns red. There is no "PUSH" label.

Just to be sure: during/after you move the Throttle to 1/3, you don't give any Brakes or ParkingBrakes command yourself, do you ?? (because if you do, that would explain what happens).
If not: what is the framerate you have when trying this ?? (if that's below 15 or so, this could explain it as well).

Another explanation could be: if you use a proportional toebrakes controller, where (when in rest) the value doesn't get below 10% (mis-calibration).
Because when between 10 and 20%, you won;t see an FSX BRAKES message .
Are you using proportional toebrakes ??
If so, I can send you a test gauge that gives the brakes values in rest position.

In regards to the jitter, I believe it also happened in V3. It happens more often in a dense scenery, less on a ship at sea - but it still happens. My machine is quite old (i7-3770 @ 3,4 GHz with 8 GB RAM), so that might contribute.
What other infos could I provide you with to help iron out the problem?

Again, low framerates (<15) may explain the problem, because of your observation that it is less on a ship then in dense scenery (causing lower framerates).
Does disabling the gauge (as suggested) solve it or not ??

By the way: my PC is less powerfull then yours, but actual framerate depends on many other factors/settings in FSX.

Rob

[PhantomTweak]

Appearantly another subtil difference (in FDE) between FSX-Accel/Steam (which we use) and P3D (your FS version).
Can Pat/Mark confirm that this also works for you ???

After I suck down some more coffee, I'll be getting on this to test those changes Maryadi posted. I always fly all Realism sliders full right, as well. Perhaps taking one down a little will also alter the roll situation. A lost of .air file settings consider the realism sliders thus: Full right, 100% effect of the setting in question, ANYthing below full right, the .air file considers 50% effect, or even 0% effect. So, just adjusting the General Realism (usually) slider to anything other than full right can have a large effect. Much larger than it seems it should, but that's how .air files work. Now, if the settings in question aren't included in the .air file, many in R1534 and higher, then the realism sliders wouldn't have much effect. Since many are over-ridden by the aircraft.cfg settings, the sliders don't matter any way, but I still leave mine full right, just to be on the safe side.
I will then, if the roll is gone, try seeing if I can figure out just which entry Maryadi added is the "secret" entry that fixes it. I'll try just adding one of those last 4 entries at a time to see which, if any, is the magical entry that fixes everything.
Again, more testing ASAP. I will post my results this afternoon (my time, PST) or at worst, this evening.

Mark,
it sounds to me like your EXE.XML got changed/corrupted somehow. Have you added, or changed, anything that could do that? This includes Windows updates, which can have unexpected effects. May I suggest you take and make a copy of your existing EXE.XML file and store it someplace safe, like in the FSX folder, since it doesn't look there for the exe.xml file. Then, make sure the only entries in the EXE.XML file in the normal location are the regular, first entry, that it comes with by default, and the AICarriers entry, unless there's another entry in it you absolutely must have to make the sim function properly. This way, we can be certain nothing is changing or altering the AICarriers entry. Then you can start adding any other entries to your EXE.XML file that you have. Remember, you have to shut FSX down, and then restart it to see any changes to the EXE.XML file. Kinda time consuming, buuuut...
Another thing to check, especially if you have gotten any Windoze updates installed, is whether your .NET Framework needed for AIC is still installed AND running. If not, you may need to reinstall it.
You can also try starting AIC manually with a shortcut to the AICarriers.exe file in the AICarriers install folder you would normally start it with the EXE.XML. Always Run As Administrator. It sounds to me like, for some reason, AIC isn't starting automatically when the sim starts any longer. Now let's see if we can figger out why
We'll get it. I'm stubborn...

By the way, I don't get the low altitude Jitter that Mr. Seawing has mentioned. I can post my computer specs if you want. I am using FSX:SE.

Be back with test results ASAP.
Pat☺

[seawing]

Just to be sure: during/after you move the Throttle to 1/3, you don't give any Brakes or ParkingBrakes command yourself, do you ?? (because if you do, that would explain what happens).
If not: what is the framerate you have when trying this ?? (if that's below 15 or so, this could explain it as well).

Another explanation could be: if you use a proportional toebrakes controller, where (when in rest) the value doesn't get below 10% (mis-calibration).
Because when between 10 and 20%, you won;t see an FSX BRAKES message .
Are you using proportional toebrakes ??
If so, I can send you a test gauge that gives the brakes values in rest position.


Again, low framerates (<15) may explain the problem, because of your observation that it is less on a ship then in dense scenery (causing lower framerates).
Does disabling the gauge (as suggested) solve it or not ??

By the way: my PC is less powerfull then yours, but actual framerate depends on many other factors/settings in FSX.

Rob

Hi Rob,

I may have both issues, I'm afraid. The frame rate may have been low (dense scenery) and I am using proportional toebrakes (though calibration seems to be fine). I will test again in a less dense area with more than 20 fps and report back! If you could send me the test gauge to rule out the brakes!?

Yes, disabeling the gauge seemed to cure it, though I initially I had Accufeel messing up the flight behaviour until I turned it of. With the disabled gauge the MV-22 hovers fine so far.

Thanks! I get up to about 30-35 fps out of the system, however, in dense areas it drops down considerably.

Seawing

[kalong]

... I will then, if the roll is gone, try seeing if I can figure out just which entry Maryadi added is the "secret" entry that fixes it. I'll try just adding one of those last 4 entries at a time to see which, if any, is the magical entry that fixes everything. ...
Be back with test results ASAP.
Pat☺

it not a secret, the " 4 " entries are mention clearly in FSX/P3D SDK documentation. that was a multipliers on the effects induced by rotating propellers, called "left turning tendencies".

[freded]

After I suck down some more coffee, I'll be getting on this to test those changes Maryadi posted. I always fly all Realism sliders full right, as well. Perhaps taking one down a little will also alter the roll situation. A lost of .air file settings consider the realism sliders thus: Full right, 100% effect of the setting in question, ANYthing below full right, the .air file considers 50% effect, or even 0% effect. So, just adjusting the General Realism (usually) slider to anything other than full right can have a large effect. Much larger than it seems it should, but that's how .air files work. Now, if the settings in question aren't included in the .air file, many in R1534 and higher, then the realism sliders wouldn't have much effect. Since many are over-ridden by the aircraft.cfg settings, the sliders don't matter any way, but I still leave mine full right, just to be on the safe side.
I will then, if the roll is gone, try seeing if I can figure out just which entry Maryadi added is the "secret" entry that fixes it. I'll try just adding one of those last 4 entries at a time to see which, if any, is the magical entry that fixes everything.
Again, more testing ASAP. I will post my results this afternoon (my time, PST) or at worst, this evening.

Mark,
it sounds to me like your EXE.XML got changed/corrupted somehow. Have you added, or changed, anything that could do that? This includes Windows updates, which can have unexpected effects. May I suggest you take and make a copy of your existing EXE.XML file and store it someplace safe, like in the FSX folder, since it doesn't look there for the exe.xml file. Then, make sure the only entries in the EXE.XML file in the normal location are the regular, first entry, that it comes with by default, and the AICarriers entry, unless there's another entry in it you absolutely must have to make the sim function properly. This way, we can be certain nothing is changing or altering the AICarriers entry. Then you can start adding any other entries to your EXE.XML file that you have. Remember, you have to shut FSX down, and then restart it to see any changes to the EXE.XML file. Kinda time consuming, buuuut...
Another thing to check, especially if you have gotten any Windoze updates installed, is whether your .NET Framework needed for AIC is still installed AND running. If not, you may need to reinstall it.
You can also try starting AIC manually with a shortcut to the AICarriers.exe file in the AICarriers install folder you would normally start it with the EXE.XML. Always Run As Administrator. It sounds to me like, for some reason, AIC isn't starting automatically when the sim starts any longer. Now let's see if we can figger out why
We'll get it. I'm stubborn...

By the way, I don't get the low altitude Jitter that Mr. Seawing has mentioned. I can post my computer specs if you want. I am using FSX:SE.

Be back with test results ASAP.
Pat☺

Pat,

Grrr! I wrote quite a long reply to you, didn't send it, then had to reboot because .NET told me to. Got back to this forum thread and my incomplete reply had GONE! Guess I'll learn from that and save anything I haven't sent before rebooting...

So here goes again, but probably shorter.

I did as you suggested and saved a backup copy of my EXE.XML and then deleted all irrelevant sections. No improvement after restarting FSX.

II also check and Repaired .NET Framework (hence the reboot!).

NOW! After that enforced reboot, I finally have the AICarriers' window coming up with Shift+J...

No idea which bit of fiddling about did it - may have been .NET. Anyway, my next step is to see if AIC still works after reinstating the backed up EXE.XML.

Time for a beer!

Mark

PS: It still works with original EXE.XML

[PhantomTweak]

I am really glad it's up and working again!
Also glad we figured it out. It was the .NET Framework. Like I said, Windows updates can have unexpected effect on the system. I'm just glad it working again.
Now, quit breaking it! LOL


As to testing Maryadi's updated [flight_tuning] section: Yes, they did seem to stop the uncommanded roll, and no one, or combination of any 2 or 3 settings alone would be effective. In other words, it took all 4 together.
My question now would be: What undesirable effect(s) on other flight characteristics will there be? Like Rob said, that effectively turns off those "Propeller-induced turning effect parameters". How will this affect the plane's flight characteristics over-all? I believe the props are counter-rotating, Would this eliminate those effects anyway? It wouldn't have an affect in Helicopter mode, but when it's airplane mode, nacelles at 0°, it basically acts like a Beech twin engine plane, just to use an example. Or a P-38. The list of twin engine planes is very long. And since either engine can power both props, the loss of one isn't as bad as in a regular twin.

Since I've been mostly involved in jets, I am not all that versed in propeller driven FDE's. Is it possible that making those settings all a very low number, like 0.01, or even 0.001, would activate the "propeller-induced turning effects", to maintain correct flight effects of the propellers while eliminating the uncommanded roll? Or reducing it to a hardly noticeable effect? Or are they even needed, given the design of the plane? I obviously have a lot still to learn!
Obviously, a lot more testing is needed.

I did notice one interesting thing, however, that may, or may not be having an effect on this situation: The plane seems to use the fuel in the right side tanks first. Could this be contributing to a weight imbalance, leading eventually to a rolling moment? When the tanks are full, and with Maryadi's settings installed, yes, the uncommanded roll is cleared up. BUT: Would the way the plane uses fuel cause it to reappear as the right side tanks are emptied? Or is it just the way the Fuel page displays what's really happening, ie: it's using the fuel equally from both an left and right sides, maintaining a balance?
Or does it even matter in FSX?

Pat☺

[seawing]

Hi Rob,

I may have both issues, I'm afraid. The frame rate may have been low (dense scenery) and I am using proportional toebrakes (though calibration seems to be fine). I will test again in a less dense area with more than 20 fps and report back! If you could send me the test gauge to rule out the brakes!?

Yes, disabeling the gauge seemed to cure it, though I initially I had Accufeel messing up the flight behaviour until I turned it of. With the disabled gauge the MV-22 hovers fine so far.

Thanks! I get up to about 30-35 fps out of the system, however, in dense areas it drops down considerably.

Seawing

Hi Rob,

it is definately not the brakes. I tried the tow/push both on a dense airport (doesn't work - around 10-12 fps) and on an oil rig in the North Sea (fps >30 -> works as advertised). So it is due to the low frame rate only, I guess.

I had inhibited the jitter gauge, it all worked fine initially (over land, ships and oilrigs) and I did some SAR and sling load flying. When I came to a frigate, though, (and later over the airport) the jitter re-appeared even with the gauge commented out. When over the frigate the fps were >30, so that shouldn't have been a factor. Any other thoughts?

Best regards,

Seawing

[rcbarend]

it is definately not the brakes. I tried the tow/push both on a dense airport (doesn't work - around 10-12 fps) and on an oil rig in the North Sea (fps >30 -> works as advertised). So it is due to the low frame rate only, I guess.

The very low FPS would explain it.
A bit technical explanation, but it may shed some light for you (and other people) on how FSX internally works.
What most probably happens here:
In FS, XML gauges are normally scheduled at a rate of 18 Hz (every 55 msec), and when an XML gauge issues an event, the coding would normally assume that the result of such an event is reflected in the state of the corresponding FS variable in the next schedule of the gauge. However, when framerate drops below 15, this is not always the case.
So what happens here:
When you have set the throttle to 1/3, the gauge issues an event to release the ParkingBrakes and sets the Tow-Active state.
But, due to the low FPS, in the next schedule of the gauge the FS variable indicates that the ParkingBrakes are still ON.
Causing the Tow feature to immediately de-activate again, because it "thinks" the user has set the ParkingBrakes ON again.

If you PM me your Email address, I will mail you a patch of the gauge that doesn't check this so it would work OK always.
Downside is, that if you would manually set ParkingBrakes ON during a TOW session, it has an odd effect.

I had inhibited the jitter gauge, it all worked fine initially (over land, ships and oilrigs) and I did some SAR and sling load flying. When I came to a frigate, though, (and later over the airport) the jitter re-appeared even with the gauge commented out. When over the frigate the fps were >30, so that shouldn't have been a factor. Any other thoughts?

I assume you haven't activated AccuFeel again ?
What I forgot to add to my readme is, that AccuFeel conflicts with my V(S)TOL solution. Not just for this MV22B, but any aircraft that has my V(S)TOL in it.
Reason being, that AccuFeel uses the same kind of tricks as I do, to simulate a "better" flightbehavior by overwriting FS variables through SimConnect.
Which conflicts, because there can't be "two captains on one ship" ...LoL

Rob

[seawing]

I assume you haven't activated AccuFeel again ?
What I forgot to add to my readme is, that AccuFeel conflicts with my V(S)TOL solution. Not just for this MV22B, but any aircraft that has my V(S)TOL in it.
Reason being, that AccuFeel uses the same kind of tricks as I do, to simulate a "better" flightbehavior by overwriting FS variables through SimConnect.
Which conflicts, because there can't be "two captains on one ship" ...LoL

Rob

Hi Rob,

thanks for shedding the light ;-) !!

No, infact it was during the same flight, so AccuFeel was still off. It actually interferes with a lot of aircraft, but somehow I can't just turn it off - it will reactivate on the next loading of FSX.

I#ll send you a PM!

Best regards,

Seawing

[rcbarend]

Hi Rob,

thanks for shedding the light ;-) !!

No, infact it was during the same flight, so AccuFeel was still off. It actually interferes with a lot of aircraft, but somehow I can't just turn it off - it will reactivate on the next loading of FSX.

I#ll send you a PM!

Best regards,

Seawing

Email with new gauge sent ....

Rob

[PhantomTweak]

Hi all!
Been a while, but I have a new, and quite perplexing problem.
As you can see in thee picture below, the NR reading on the STAT screens, both the center console, the small black and white screen above it, and the MFD STAT screen ENG page, show it to be apparently operating sort of backwards.


When I first load the plane in, it reads 158, and once the engines settle down, and it's ready to fly, as I increase the throttle is drops to 35 or about that. The area colored in as the reading changes, also seems backwards, with the black being the reading, and the green being the "empty" area, reversed from all the other gauges.
The engines function perfectly normally, all other engine readings are well within normal parameter throughout their range. Just the NR is in error. I also have a constant Master Caution light.

I am quite puzzled. I have changed NOTHING in the aircraft.cfg, other than the Flight_Tuning parameters discussed above, nor have I touched the .air file.
Any help that can be provided will be greatly appreciated. It doesn't change the way the plane operates, it's just a display problem, I think.
Have fun everyone!
Pat☺

[kalong]

Hi all!
Been a while, but I have a new, and quite perplexing problem.
As you can see in thee picture below, the NR reading on the STAT screens, both the center console, the small black and white screen above it, and the MFD STAT screen ENG page, show it to be apparently operating sort of backwards.


When I first load the plane in, it reads 158, and once the engines settle down, and it's ready to fly, as I increase the throttle is drops to 35 or about that. The area colored in as the reading changes, also seems backwards, with the black being the reading, and the green being the "empty" area, reversed from all the other gauges.
The engines function perfectly normally, all other engine readings are well within normal parameter throughout their range. Just the NR is in error. I also have a constant Master Caution light.

I am quite puzzled. I have changed NOTHING in the aircraft.cfg, other than the Flight_Tuning parameters discussed above, nor have I touched the .air file.
Any help that can be provided will be greatly appreciated. It doesn't change the way the plane operates, it's just a display problem, I think.
Have fun everyone!
Pat☺

need confirmation: did you make any update on dll gauge?

will investigate it.

[rcbarend]

Weird ....
Is this in Accel or Steam ????

I'm using Accell, and it works fine for me.


Another thing I noticed in your Picture:
The MWGB value (maybe Maryadi will explain what that value is) in the EICAS screen reads 0 with you; for me, it reads value 462, with the corresponding green segment displayed.

PS:
Pat, is this problem with the version of file Mar_MV22B.dll in the panel folder, I provided in Addon4 zip file ?? (creation date May 7th 2017, size 490 kB)

@Maryadi: tried all versions of the dll I have since Rel1 (incl. the VS2015 one); all works the same (properly) for me.

[kalong]

Weird ....
Is this in Accel or Steam ????

I'm using Accell, and it works fine for me.


Another thing I noticed in your Picture:
The MWGB value (maybe Maryadi will explain what that value is) in the EICAS screen reads 0 with you; for me, it reads value 462, with the corresponding green segment displayed.

PS:
Pat, is this problem with the version of file Mar_MV22B.dll in the panel folder, I provided in Addon4 zip file ?? (creation date May 7th 2017, size 490 kB)

@Maryadi: tried all versions of the dll I have since Rel1 (incl. the VS2015 one); all works the same (properly) for me.

MWGB get value from PRGB, if it 0 value, it seem PRGB 1 have opposite value. thinking ... a possibility flight tuning give effect on engine parameter. I need more info... please remember any change on Osprey aircraft.cfg / air file, an add on that control / make modification to get reality flight. Osprey dll gauge still simple code that get value from aircraft.cfg and air file.

@rcbarend nicely done for VS2015 dll gauge, I'll send AVM.dll (VS2015) soon. still testing on P3D v4, FSX camera gauge make P3D v4 got CTD. I need new refuel gauge without FSX camera gauge, plus still waiting doug refuel gauge 64 bit

[PhantomTweak]

It's FSX:SE.
It's the add-on from Mr. Rob v4 from rcb_MV22B1_Addon4.zip.
Only changes to the aircraft.cfg are the Sling Load entries I modified, a lights add-on to make the VC more visible at night from mv_22b_vc_mods.zip, a strobe light change from this file: JS_V22B_NavStrobe.zip, and the Flight_Tuning entries you provided. I DID change the first one, p_factor_on_yaw to 0.001 as a test. I don't see how that could cause this, but I can zero it again to test it, if you think I should.
I can reinstall it from the zip file to with no changes to anything to test. That was my next step anyway. Install one add-on at a time until it happens again...
Pat☺

EDIT:

PS:
Pat, is this problem with the version of file Mar_MV22B.dll in the panel folder, I provided in Addon4 zip file ?? (creation date May 7th 2017, size 490 kB)

Yes, it is. Sorry, I forgot to answer that originally.
Another thing I forgot to say: Many thanks go out to you both for the quick responses. I really appreciate it!
Finally:

The MWGB value (maybe Maryadi will explain what that value is) in the EICAS screen reads 0 with you;

On mine, it goes to 0 when the engines have been running high enough to hover, then are brought to idle with the F1 key. About 89 to 92 N1, give or take...
Pat☺

[seawing]

Email with new gauge sent ....

Rob

Hi Rob,

again, thanks for the revised gauge. It tested it both in simple and complex sceneries and it works everywhere!

Regarding the jitter, it seems memory depended, as it mainly happens in complex areas and usually starts at the moment the ground dirst/sand blast effect sets in. However, if I take-off from complex aerodromes, it doesn't happen in the beginning. On the other side even on ships out at sea it does happen after a long flight.

best regards,

Seawing

[rcbarend]

Hi Rob,

again, thanks for the revised gauge. It tested it both in simple and complex sceneries and it works everywhere!

Regarding the jitter, it seems memory depended, as it mainly happens in complex areas and usually starts at the moment the ground dirst/sand blast effect sets in. However, if I take-off from complex aerodromes, it doesn't happen in the beginning. On the other side even on ships out at sea it does happen after a long flight.

best regards,

Seawing

Aha .... this is not the "jitter" we discussed, but simply "stutters", probably caused by the CPU not been able to keep sending data to the videocard. Or maybe low on free memory.
Try this... just remove the smoke.system definitions from the aircraft.cfg ( so there's no more grounddust effect) and see if this helps.
Rob

[kalong]

making test for any possibility on new 4 entries on [flight_tuning], PRGB and MWGB not affected.