KC-137R family project

Everything in connection with developing aircraft for FlightGear
User avatar
J Maverick 16
Posts: 757
Joined: Sun Nov 08, 2015 3:16 pm
Location: Northern-Italy
Contact:

Re: KC-137R ATAARS project, need some help.

Postby J Maverick 16 » Sat Apr 30, 2016 8:54 am

"Let's Roll!"

Image

Image

Image

New KC-137R USAF livery done by me.
Regards, Mav
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.

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

Re: KC-137R ATAARS project, need some help.

Postby Octal450 » Sat Apr 30, 2016 2:12 pm

@J-Mav16, nice, is it on GIT?

I just got my new GTX960, and Windows Vista reinstalled, so I'm ready to fly again!

Regards,

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

Re: KC-137R ATAARS project, need some help.

Postby J Maverick 16 » Sat Apr 30, 2016 2:23 pm

it0uchpods wrote:@J-Mav16, nice, is it on GIT?

I just got my new GTX960, and Windows Vista reinstalled, so I'm ready to fly again!

Sent you all the details via e-mail.
Regards, Mav
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.

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

Re: KC-137R ATAARS project, need some help.

Postby Octal450 » Sat Apr 30, 2016 2:34 pm

@J-Mav16
rgr

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

Re: KC-137R ATAARS project, need some help.

Postby Octal450 » Sat Apr 30, 2016 2:45 pm

And the damage code is pushed to GIT.

User avatar
IAHM-COL
Posts: 6455
Joined: Sat Sep 12, 2015 3:43 pm
Location: Homey, NV (KXTA) - U.S.A
Contact:

Re: KC-137R ATAARS project, need some help.

Postby IAHM-COL » Sat Apr 30, 2016 2:59 pm

Way to go!
https://raw.githubusercontent.com/IAHM-COL/gpg-pubkey/master/pubkey.asc

R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?

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

Re: KC-137R ATAARS project, need some help.

Postby J Maverick 16 » Sat Apr 30, 2016 3:34 pm

Josh could you have a look at onox's model of the 707TT?

https://github.com/onox/707
https://github.com/l0k1/707 (version used by OPRF Crew).
I'm doing the longest flight ever done by myself with the KC, KIAB>KSUU with many waypoints. I'll start the last leg (KSLV>KSUU) soon. Then we can try the damage code and also try to work on some more stuff.
Regards, Mav
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.

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

Re: KC-137R ATAARS project, need some help.

Postby J Maverick 16 » Sat Apr 30, 2016 4:09 pm

UPDATED TO-DO LIST IN ORDER OF IMPORTANCE (first seven points should be fixed before May 1st):
1) work on fuel tanks and payloads (reduce available payload and add a standard load, increase fuel tanks load and implement fuel consumption while refueling).
2) Yet again fix problems with Autopilot: Altitude Hold does not correspond to the real FL the KC maintains and the GPS/FMS hdg keeps disabling randomly while flying, especially when altitude is changed.
3) work on the boom operator office (new instruments (AI), fix the point of view in RT (makes the rear aircraft part invisible), etc. + onox)

4) make the gear animation faster.
5) improve internal + engines sounds.
6) test damage code.
7) USAF liveries (ACI's job + J Mav)

8) improve ATA refueling (onox model)
9) make the CDUs work properly + resize, reposition and retexture them.
10) put new radio comms under the throttle levers.
11) make the reverse thrust viewable on the engines display.
12) add a MFD between the two CDUs which works as TCAS, systems, and other.
13) 3D engines models: UV map, smoke.
14) work on both engineer and overhead panel (improve instruments and move sone from the eng to the oh).
15) Switch the "Autopilot view" to "Overhead panel view".
16) add 787-9 HUD to both pilot and co-pilot.
17) improve the magnetic compass instrument (make it fixed and place a new compass).
18) improve the trims.
19) add a few passenger seats to the cabin.
20) remove/move the "Rolex" in the middle of the cockpit.
21) make a whole new AP panel in the center part of the cockpit (where the current one stays).
22) implement MP dual control for co-pilot and boom operator.
23) remove cargo loaders.

This is the lot, then we'll have a break and start on the AWACS.
Regards, Mav
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.

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

Re: KC-137R ATAARS project, need some help.

Postby Octal450 » Sat Apr 30, 2016 4:59 pm

J Maverick 16 wrote:UPDATED TO-DO LIST IN ORDER OF IMPORTANCE (first seven points should be fixed before May 1st):
1) work on fuel tanks and payloads (reduce available payload and add a standard load, increase fuel tanks load and implement fuel consumption while refueling).
2) Yet again fix problems with Autopilot: Altitude Hold does not correspond to the real FL the KC maintains and the GPS/FMS hdg keeps disabling randomly while flying, especially when altitude is changed.
3) work on the boom operator office (new instruments (AI), fix the point of view in RT (makes the rear aircraft part invisible), etc. + onox)

4) make the gear animation faster.
5) improve internal + engines sounds.
6) test damage code.
7) USAF liveries (ACI's job + J Mav)


Hmm OK...

1) No reason to add a load, pilots can just add it themselves in Fuel and Payload. I do not know how to do fuel consumption while refueling. I have only been developing for 3 monthes!!!
2) I will change to my autopilot as soon as able.
3) Could not add AI due to the way the top panel is made, it would waste to much time, we could just put it on the panel. I don't understand why the rear it invisable in the RT, but not in the R.
4) It is at the correct speed of the real aircraft.
5) I did not receive sounds from you.
6) Fine.
7) Fine.

All that pefore May 1? You must think I'm made of time.

Regards,

User avatar
IAHM-COL
Posts: 6455
Joined: Sat Sep 12, 2015 3:43 pm
Location: Homey, NV (KXTA) - U.S.A
Contact:

Re: KC-137R ATAARS project, need some help.

Postby IAHM-COL » Sat Apr 30, 2016 5:12 pm

it0uchpods wrote:All that pefore May 1? You must think I'm made of time.

Regards,


That is tomorrow :shock: :mrgreen:
https://raw.githubusercontent.com/IAHM-COL/gpg-pubkey/master/pubkey.asc

R.M.S.
If we gave everybody in the World free software today, but we failed to teach them about the four freedoms, five years from now, would they still have it?


Return to “Aircraft Development”

Who is online

Users browsing this forum: No registered users and 4 guests