IDG A32X Development Archive - Closed

[J Maverick 16]

I just pushed a few update:
* Much improve Canvas performance
* Fix some bugs
* Save options in file, so they share between -sets

I went from 25FPS to 40-60FPS (depending on scenery, etc) It's a start, but there is still more optimization needed.

Now, I am working on the APU Bleed shutdown delay.

Also, you can now change the DU update rate, and slow it if you need to: Aircraft Config --> DU Framerate:

This setting is saved in between sessions, and inbetween -set files. (but A33X and A32X setting files are seperate)

Josh

Regards, Mav

[V12]

Superb job IDG ! Framerate is far better than previous version.

[Octal450]

Hi All,
Thanks to program I wrote, this account will post some updates here every so long on new things going on, as while I do not active in the forums anymore, I still will update here with the work being done. This decision was reached after reaching some information on Discord that users did not know what was new.

Please note that I may not reply for several days to inquires or requests. See signature for more information.
Josh

[CaptB]

I have not posted here for some time. Here's a small teaser on the 3D model:

[glofix]

First of all, congrats on the amazing work you are doing with this models

I don't know if this is the correct place to ask this but here I go.

I'm touching the code for learning purposes and I'm trying to do some local modification. I decided something easy so I'm trying to make the DIM and BRT buttons operative in the MCDU. So far I've managed do all that is needed to change up/down the brightness property in 0.2 steps between 0.0 and 1.0. Nasal console shows proper values when printing them so all seems to be working fine to this point.

I've also added this code for mcdu1 (and the corresponding one for mcdu2):

Code: Select all

  <animation>
    <type>material</type>
    <object-name>mcdu1.screen</object-name>
    <emission>
      <red>1</red>
      <green>1</green>
      <blue>1</blue>
      <factor-prop>MCDU[0]/brightness</factor-prop>
    </emission>
  </animation>


But the MCDU display doesn't change color intensity or switches off when brightness is 0 (e.g. PFD displays). No related errors in log and the plane works as usual. I've checked the ac files and all seems correct. I can't find what I'm missing.

Do I have to specify something else for the mcdu screens to dim its emission?

Another question I have. Are both MCDU exactly the same? (mcdu1 on on ac1 / mcdu2 on ac2). If so, why not have only a Nasal/MCDU/MCDU.nas instead of two and pass an mcdu id parameter to their functions to avoid duplicated nasal code?

Sorry if this is not the place or I'm bothering you with my questions. As I said, awesome job and thank you to the team.

[Octal450]

Good morning glofix,
yes, there is a way. But sadly this already is done in my WIP build. Sorry for the waste of your time.

Well, that is because back when I made this files I did not know you could do that in nasal, and never bothered to change it. But it will likely be corrected soon.

Thank you very much for you compliments.

Best Regards,
Josh

[glofix]

Learning is never a waste of time . Will check your solution when you release the build.

[V12]

Ground speed on ND is everytime same as TAS, no matters of the wind direction and speed.
Example :
GS 430 kts, TAS 430 kts, tailwind 25 kts.
In this case GS should be 455 kts.

Fresh observation :
Probably, correct is GS, not TAS, because GS was changed after wind direction change.

Next example :
I used standard ISA calculator from http://www.newbyte.co.il/calculator.php :
FL210
CAS 300 kts
TAS on ND 440 kts
GS on ND 440 kts, tailwind 35 kts

By calculator, TAS should be 406 kts, what is result GS-tailwind.

[Octal450]

Good day V12, this will be addressed soon, thank you.

Moved the FlyByWire to JSBsim
Will work on reducing the bugs/issues greatly, then FMGC works start.

IDG Team

[CaptB]

NLG mesh remodeled:

[V12]

Good day V12, this will be addressed soon, thank you.

Moved the FlyByWire to JSBsim
Will work on reducing the bugs/issues greatly, then FMGC works start.

IDG Team

Thank You for quick fix, now is GS/TAS calculated properly.

[DylanTL]

I was too lazy to read this thread so I'm just gonna ask: When will the MCDU be fully functional? If someone has an answer I'd be glad to hear it.

Thanks,

Dylan

[Octal450]

All I can say is by V1.0.

Josh

[merspieler]

For the MCDU to be fully functional the FMGS has to be done, Josh said IIRC that he don't expect it to be done before september.
But we all have a real life which has priority which means that this is NOT a fix date where you can expect it but just an estimation.
So you have to wait some time.

[Octal450]

September was guessed a while ago l, due to my extensive medical issues I haven't done much work in it recently. As they solve up, I also need to focus on school. I would say it could be slot longer than that, don't think I'll make 4 months...

J