KC-137R family project

Everything in connection with developing aircraft for FlightGear
Octal450
Posts: 2184
Joined: Sun Oct 18, 2015 2:47 am

Re: KC-137R family project

Postby Octal450 » Thu Dec 29, 2016 2:07 pm

:D

User avatar
J Maverick 16
Posts: 757
Joined: Sun Nov 08, 2015 3:16 pm
Location: Northern-Italy
Contact:

Re: KC-137R family project

Postby J Maverick 16 » Thu Dec 29, 2016 6:34 pm

UPDATED TO-DO LIST IN ORDER OF IMPORTANCE (deadline: February 2017):

COMMON:
1) Rework completely and integrate both engines display and systems display and feature an additional nav display to fit the Block 45.
2) update overhead panel. (rework EFB textures, update EFIS controller)
3) add an AoA indicator (SHM has made both instruments and texture, need someone to refine them plus create the code).
4) Work on new splash screens for all versions (done: KC, RT, E-8, C). JMav
5) Improve Stby-AI instrument for EC/RC to make it more like a PFD.
6) Implement efficient TACAN nav system (replace DME with display).
7) rework engines 3D, UV map and animations + sounds.
8) add tail light.
9) Build new AP and AP status panels.
10) Rework completely the EADI.

KC-137R /-RT:
1) improve ATA refueling (create a working refueling code, RT 3D refuel hose) 411, JMav
2) improve the airframe 3D models (Martien VDP)
3) New liveries (JMav)
4) Implement ECM with Northrop Grumman Guardian LAIRCM (RT).

EC-137R:
1) improve a lot the AWACS officer area by adding maps, NDs, upgrade/remove current instruments, reworking 3D, etc. 411, JMav (searching volunteers)
2) Create a new set of liveries. (JMav).
3) Implement ECM.

RC-137R:
1) rework livery texture according to new model + make a new set of liveries (JMav).
2) implement advanced military recon systems. (searching for experts...)
3) Implement ECM.

E-8R:
1) implement ground surveillance systems with targeting and similar. (searching for experts...)

C-137R:
1) Fix/add new textures. 411, JMav
2) new liveries (JMav, MD-GRK).

This is the lot.
Regards, Mav
Last edited by J Maverick 16 on Thu Jan 12, 2017 9:09 pm, edited 3 times in total.
Breakin' the sound barrier every day!

Scenery designer, basic livery maker, aircraft developer (current project: F-16).
Using Thrustmaster FCS Flight Pack.
Follow me also on Instagram & Twitter @j_maverick16, Google+ and YouTube.

OPFOR77
Posts: 208
Joined: Wed Apr 27, 2016 7:30 pm

Re: KC-137R family project

Postby OPFOR77 » Sun Jan 01, 2017 6:55 am

Bug reports?

When you change the nav radio to a frequency ending in .000, the first bit is off. For instance, tuning to the MWH VOR with freq 115.000, the screen will display 114.000.

The radial knob range, while initially showing 000, can only be turned down to 001 after messing with it. Additionally, the max setting is 361.

Picture: https://i.imgur.com/ZXT5zbm.png
Both NAV1 active and standby freqs are set to 115.000

e: also, can't hear ATIS.

e2: any way to use VOR R other than letting it point directly at the VOR?
OPRF Fighter Jock and Dev

Octal450
Posts: 2184
Joined: Sun Oct 18, 2015 2:47 am

Re: KC-137R family project

Postby Octal450 » Sun Jan 01, 2017 4:53 pm

@OPFOR77
Thanks for the report. I'll check this right now...

Octal450
Posts: 2184
Joined: Sun Oct 18, 2015 2:47 am

Re: KC-137R family project

Postby Octal450 » Sun Jan 01, 2017 5:00 pm

I've fixed the radial knob bug. <wrap> should have been true.

Radios work fine here FG2016.1.2
http://prntscr.com/dqc1hd

Can't hear ATIS because the volume is down. When we add the radio volume panel, will be fixed.

e2: don't understand.

OPFOR77
Posts: 208
Joined: Wed Apr 27, 2016 7:30 pm

Re: KC-137R family project

Postby OPFOR77 » Sun Jan 01, 2017 7:19 pm

The radios not displaying the correct number is due to a lack of a <bias> tag in the instrument's xml file. I added a <bias>0.0005</bias> and it worked like a charm.

e: also the min/max's for the radio.freq.knob are wrong. You have

Code: Select all

         <step>-0.025</step>
         <min>000</min>
         <max>975</max>
         <wrap>true</wrap>


and it should be

Code: Select all

         <step>0.025</step>
         <min>108</min>
         <max>118</max>
         <wrap>true</wrap>


e2: same thing for the comm radios

e3: if you're not allowing the radial knob to go to 000, you should set it so it doesn't initialize at 000. Looks funny like it is.
OPRF Fighter Jock and Dev

Octal450
Posts: 2184
Joined: Sun Oct 18, 2015 2:47 am

Re: KC-137R family project

Postby Octal450 » Sun Jan 01, 2017 7:32 pm

@OPFOR77
OK. I make the change of 360.

THE RADIOS work fine as they are? I don't understand.

I'll change the minmax tho.

Can you show me what exact steps you take to cause problems?
The knobs WORK CORRECTLY. I don't understand.

OPFOR77
Posts: 208
Joined: Wed Apr 27, 2016 7:30 pm

Re: KC-137R family project

Postby OPFOR77 » Sun Jan 01, 2017 8:53 pm

The issue is because not all of your textranslate animations have <bias> tags. It might work fine for you and not someone else due to how floating point precision works.
OPRF Fighter Jock and Dev

Octal450
Posts: 2184
Joined: Sun Oct 18, 2015 2:47 am

Re: KC-137R family project

Postby Octal450 » Sun Jan 01, 2017 9:17 pm

Ahh.
Makes sense, I'll add a bias value.

OPFOR77
Posts: 208
Joined: Wed Apr 27, 2016 7:30 pm

Re: KC-137R family project

Postby OPFOR77 » Sun Jan 01, 2017 9:26 pm

And coming back to the VOR thing (and sorry for not explaining it well), is there a way to show the co-pilots VOR on the EFIS? Right now it just shows DME, but there's no way to use the radials that I can see. I may be missing it.

For instance, in this pic: https://i.imgur.com/iH1pEeJ.png I have VOR L tuned to the GEG VOR, and VOR R tuned to the COE VOR, but I see no way to actually use the COE VOR other than the DME and the green arrow.
OPRF Fighter Jock and Dev


Return to “Aircraft Development”

Who is online

Users browsing this forum: No registered users and 11 guests