@Jmav16
You are really learning alot about developing.
Great job!
PS: I'm on mumble now
Josh
KC-137R family project
Re: KC-137R ATAARS project, need some help.
OK guys: Updates to stuff + CDUs is on GIT.
WARN!!! CDUs have some bugs, we fix soon!
Garmin is next... Maybe tonight?!?!?!?!?
Josh
WARN!!! CDUs have some bugs, we fix soon!
Garmin is next... Maybe tonight?!?!?!?!?
Josh
- 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.
UPDATED TO-DO LIST IN ORDER OF IMPORTANCE (deadline TBD):
KC-137R:
1) continue working on the systems display.
2) improve the trims (using 757/787 as reference).
3) work on fuel tanks and payloads (reduce available payload and add a standard load, implement fuel consumption while refueling, onox as reference).
4) improve ATA refueling (boom texture and model + code, onox model)
5) add refueling probe model to the RT so it can be refueled (+ code).
6) Engines: smoke, contrails.
9) work on both engineer and overhead panel (improve instruments and move some from the eng to the oh).
10) remove/change cargo loaders (onox model)
11) implement MP dual control for co-pilot and boom operator.
12) knife the boom and edit it.
EC-137R:
2) improve a lot the AWACS officer area by adding maps, NDs, upgrade/remove current instruments, reworking 3D, etc.
3) add an MFD between the CDUs which works as advanced radar.
4) improve the airframe 3D model (searching volunteers)
5) Engines: smoke, contrails.
6) implement MP dual control for co-pilot and AWACS officer.
RC-137R:
1) start everything by using CFM engines, AWACS cockpit and office, mixed textures (mainly KC).
2) rework livery texture (JMav).
3) implement advanced military systems.
4) improve the airframe 3D model (searching volunteers)
E-8R:
1) start everything by using IAE engines, KC cockpit and AWACS office, mixed textures (mainly AWACS).
2) improve the airframe 3D model (searching volunteers).
3) liveries (JMav).
C-137R:
1) start everything by using IAE engines, AWACS cockpit, new textures.
2) liveries (JMav).
This is the lot.
Regards, Mav
KC-137R:
1) continue working on the systems display.
2) improve the trims (using 757/787 as reference).
3) work on fuel tanks and payloads (reduce available payload and add a standard load, implement fuel consumption while refueling, onox as reference).
4) improve ATA refueling (boom texture and model + code, onox model)
5) add refueling probe model to the RT so it can be refueled (+ code).
6) Engines: smoke, contrails.
9) work on both engineer and overhead panel (improve instruments and move some from the eng to the oh).
10) remove/change cargo loaders (onox model)
11) implement MP dual control for co-pilot and boom operator.
12) knife the boom and edit it.
EC-137R:
2) improve a lot the AWACS officer area by adding maps, NDs, upgrade/remove current instruments, reworking 3D, etc.
3) add an MFD between the CDUs which works as advanced radar.
4) improve the airframe 3D model (searching volunteers)
5) Engines: smoke, contrails.
6) implement MP dual control for co-pilot and AWACS officer.
RC-137R:
1) start everything by using CFM engines, AWACS cockpit and office, mixed textures (mainly KC).
2) rework livery texture (JMav).
3) implement advanced military systems.
4) improve the airframe 3D model (searching volunteers)
E-8R:
1) start everything by using IAE engines, KC cockpit and AWACS office, mixed textures (mainly AWACS).
2) improve the airframe 3D model (searching volunteers).
3) liveries (JMav).
C-137R:
1) start everything by using IAE engines, AWACS cockpit, new textures.
2) liveries (JMav).
This is the lot.
Regards, Mav
Last edited by J Maverick 16 on Wed Aug 10, 2016 1:45 pm, edited 5 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.
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.
Re: KC-137R ATAARS project, need some help.
J Maverick 16 wrote:This is the lot.
Regards, Mav
Each to do list says that, I wonder if you still put this when only 2 items left I'm on mumble now.
Josh
- 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.
KC-137R-RT:
EC-137R:
Git doesn't work BTW...
Regards, Mav
EC-137R:
Git doesn't work BTW...
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.
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.
Re: KC-137R ATAARS project, need some help.
cockpits updated with status display below EICAS, NAV display below PFD in KC.
- 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.
Updated TODO list above. Hope to restart working on 'em pretty soon.
Regards, Mav
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.
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.
Re: KC-137R ATAARS project, need some help.
@JMav16
We start work tomorrow.
I want to finish a few things now before we continue the todo list.
Then the cockpit of KC/EC will be I think done for now, I'll post some fancy pics!
@IAHM-COL
Sorry for the late response.
Mr 707s (aka Mark?) AP:
The 707 has a very odd issue with heading hold. Also, the AP is not precise enough for these new engines. When you add power, the plane would swing upwards, and when you reduce power, it would swing down, then try to correct, overcorrect, and keep trying. This didn't happen with the 707, since it's engines didn't cause as much as an effect on the pitch. It also would switch of the NAV/GPS mode randomly.
The modified SYS8 controllers in my AP are much quicker to react, therefore solving this issue.
Also, the nasal controller for my AP requires a button input to change modes. It cannot change modes itself, except for ALT-CAPTURE/FLCH, ALT-CAPTURE/VS, or THR/IDLE/CLB.
I did mean no offence to Mark, his work is amazing!
I think I'm going to refer to these controllers as SYS8IT from now on, since they are from SYS8, but modified by me, with help/guidance from @jwocky.
Josh
We start work tomorrow.
I want to finish a few things now before we continue the todo list.
Then the cockpit of KC/EC will be I think done for now, I'll post some fancy pics!
@IAHM-COL
Sorry for the late response.
Mr 707s (aka Mark?) AP:
The 707 has a very odd issue with heading hold. Also, the AP is not precise enough for these new engines. When you add power, the plane would swing upwards, and when you reduce power, it would swing down, then try to correct, overcorrect, and keep trying. This didn't happen with the 707, since it's engines didn't cause as much as an effect on the pitch. It also would switch of the NAV/GPS mode randomly.
The modified SYS8 controllers in my AP are much quicker to react, therefore solving this issue.
Also, the nasal controller for my AP requires a button input to change modes. It cannot change modes itself, except for ALT-CAPTURE/FLCH, ALT-CAPTURE/VS, or THR/IDLE/CLB.
I did mean no offence to Mark, his work is amazing!
I think I'm going to refer to these controllers as SYS8IT from now on, since they are from SYS8, but modified by me, with help/guidance from @jwocky.
Josh
- 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.
it0uchpods wrote:@JMav16
We start work tomorrow.
I want to finish a few things now before we continue the todo list.
Then the cockpit of KC/EC will be I think done for now, I'll post some fancy pics!
Nice!
What are these few things? ITAF?
Ehm, now have the trouble that we need a working radar on all the cockpits and yet we don't have trim controllers...
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.
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.
Re: KC-137R ATAARS project, need some help.
Yes OK.
ITAF is IT-AUTOFLIGHT
Josh
ITAF is IT-AUTOFLIGHT
Josh
Return to “Aircraft Development”
Who is online
Users browsing this forum: No registered users and 0 guests