Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Crew communication
Omaniac
post 27/04/2009, 1:25
Post #1


50<100 posts
***

Group: Member
Posts: 84
Joined: 05/02/09
Member No.: 5881



I've finally managed to properly install the Maddog. Now almost everything works as it should, even my autobrakes during landing.
One thing is missing, and that is my crew communication. When I bring up the menu, it's shaded (grey text) and I can't select the commands. The green V is missing as well.
You guys know anything about this?

I've found a possible reason why the speed sometimes suddenly drops during climb. I did a flight from A to B. During climb and above 10000 ft, the speed increased above 250 kts as it should.
On legs page I then selected direct to a point near B, and the speed dropped to 250 kts while I still was climbing. This waypoint had a crossing altitude below 10000 ft and appeared as (example) POINT 250/8000 on my legs page.
This is where the FMC gets confused and think the speed now should be 250.
So what do you do when this happens? You can increase the speed at the waypoint (Like 280/8000) until you reach your cruising altitude, then input 250 again. Or you can use FMC override during climb and back to normal after level off.
Or use basic modes (non FMC), it's up to you.

I've put most performance sliders in the manager to the left, except refresh and vector. This made a huge difference in FPS, and almost no reduction in how it looks. I'm talking VC.

Ever wondered which model is best? Super 80 PRO or the Maddog 2008 PRO?

Wonder no more, the Maddog is way above the Super 80 in all aspects.

I've tried both.
Go to the top of the page
 
+Quote Post
Paul J
post 27/04/2009, 3:39
Post #2


>500 posts
******

Group: Member
Posts: 869
Joined: 13/12/08
Member No.: 5615



QUOTE (Omaniac @ 27/04/2009, 1:25) *
Ever wondered which model is best? Super 80 PRO or the Maddog 2008 PRO?

Wonder no more, the Maddog is way above the Super 80 in all aspects.

I've tried both.


User Manual, p12 - 14. It does work, but is too fiddly for me. I use FS Passengers, as this is approaching "as real ads it gets" and gives a printed report prior to shutdown - even including your touchdown deck angle and sink rate.

I have both, too, and totally agree, Omaniac, but for a non-atpl she's a tough nut to chew, particularly when all we have to go on is the AOM, a "User Guide" which only shows the very basics of the interface, and a flight between a couple of Italian airports. However, complaining gets us nowhere, and the manuals won't change themselves.

In that light I have to say a big Thank You to yourself for your very expert technical input here, with the same sentiment going to a number of the other gentlemen (you know who you are!). The CoolSky/Flight1 version may have a very friendly and very well supported forum, but the questions over there are to no degree as technical as those in this forum. It seems to me that the LSH version was built by pilots for pilots, and it's sure appreciated when r/w crew members chime in with the correct solution to a question, and quite comforting to know that r/w aircrew actually do use this simulation and prefer this aircraft/version ahead of all others.

thumbsup.gif



--------------------


Good things are seldom cheap, and cheap things are seldom good...

Water-cooled i7-2600K@5.0gig, ASUS P8P67 B3 DeLuxe; EVGA GTX580; 8gig Corsair Vengeance C8-1T@1600; Win 7-64; TH2G w/3x19" Viewsonic VA926; Homebuilt airliner-style yoke and pedals; 6-pack throttle quadrant; TrackIR5; No blurries.
Go to the top of the page
 
+Quote Post
Omaniac
post 04/05/2009, 23:20
Post #3


50<100 posts
***

Group: Member
Posts: 84
Joined: 05/02/09
Member No.: 5881



The problem is I've lost my crew and ground communications completely.
I'm not able to use any of those commands (external power, de ice, etc), they are there but shaded, so nothing happens when I try to select them.

Thanks Paul, but I'm only able to help on the "real" part. When it comes to software, you and Michael are the ones to thank.

Go to the top of the page
 
+Quote Post
Paul J
post 05/05/2009, 3:49
Post #4


>500 posts
******

Group: Member
Posts: 869
Joined: 13/12/08
Member No.: 5615



Check out this post, Om:-

http://www.flythemaddog.com/forum/index.ph...amp;#entry26377

It maight have the answer..... thumbsup.gif


--------------------


Good things are seldom cheap, and cheap things are seldom good...

Water-cooled i7-2600K@5.0gig, ASUS P8P67 B3 DeLuxe; EVGA GTX580; 8gig Corsair Vengeance C8-1T@1600; Win 7-64; TH2G w/3x19" Viewsonic VA926; Homebuilt airliner-style yoke and pedals; 6-pack throttle quadrant; TrackIR5; No blurries.
Go to the top of the page
 
+Quote Post
Omaniac
post 05/05/2009, 11:20
Post #5


50<100 posts
***

Group: Member
Posts: 84
Joined: 05/02/09
Member No.: 5881



Thanks, that post solved it for me.
Turns out I did not select INT on the comm panel. Before I reinstalled, I always used "ready to start" and that option had the comm panel set at INT when Maddog launced.
Now I use "Cold & dark", so I have to select INT myself.

Go to the top of the page
 
+Quote Post
Paul J
post 05/05/2009, 14:56
Post #6


>500 posts
******

Group: Member
Posts: 869
Joined: 13/12/08
Member No.: 5615



QUOTE (Omaniac @ 05/05/2009, 12:20) *
Now I use "Cold & dark".


Always... Perfect!

laugh.gif


--------------------


Good things are seldom cheap, and cheap things are seldom good...

Water-cooled i7-2600K@5.0gig, ASUS P8P67 B3 DeLuxe; EVGA GTX580; 8gig Corsair Vengeance C8-1T@1600; Win 7-64; TH2G w/3x19" Viewsonic VA926; Homebuilt airliner-style yoke and pedals; 6-pack throttle quadrant; TrackIR5; No blurries.
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic

 



Lo-Fi Version Time is now: 19/06/13 - 10:57