|
Post by anderscn on Mar 13, 2011 11:29:30 GMT
Hello,
I have a couple of questions; On most other aircraft I have flown in FS, the single-lined arrow shows the direction of the Nav1 station, whereas the double-lined arrow is the Nav2 station. However, on the HJG Tristar this is opposite. I just wonder if this would be a special Lockheed layout?
Secondly, when flying a flight with more than 9 waypoints using INS, how do I add the additional WPT´s in wpt 0,1,2 etc. during flight, for instance when being at the 7-8 or 8-9 leg? I have switched the dial to the position WPT, pressed the INSERT botton, but nothing happens. Am I missing something here?
Otherwise, a terrific plane I really enjoy.
BR, Anders
|
|
|
Post by Dan K. Hansen on Mar 13, 2011 17:40:56 GMT
I think you should select WPT 0 - press Clear - and then Insert your next waypoint just like you did the previous ones, then 1 and 2 etc. etc. Once the smaller numbers becomes obsolete, you should be able to "Fill up" again from the start ... bit by bit ....
I seem to remember that on the DC-8 you have the option to select which needle you want to show either NAV1 or NAV2 ... so shouldn't really matter...
|
|
|
Post by louross on Mar 14, 2011 15:08:54 GMT
I was also going to mention this as my No. needle is from the No. 2 Nav and the No. 2 needle (double needle) indicates the No. 1 Nav. Any way to correct this in the cgf. ile? Thanks, lr.
|
|
|
Post by aerofoto - HJG Admin on Mar 14, 2011 20:11:06 GMT
AH OK .... I see what you're meaning/where you're comming from now ! ;D A number of the original KM panels do come with NAV RADIO related issues .... as did these 2 particular panels too before we got the NAV RADIO working how it currently functions. I dunno if it's RADIOS/CFG related I just tried experimenting .... by changing some of the NAV RADIO data in the CFG, but, that achieved nothing .... so .... I suspect this could be a gauge related issue (mixed references for those needles maybe) .... only gauges aren't my specialty ! Short of suggesting "maybe" subsituting that particular current CFG gauge reference for that of a similar gauge, from another panel, which does have indicators that do work correctly .... then I can't, at this time, offer any solution ! George might be able to throw some light on this whenever it's convenient for him to do so ! Mark C AKL/NZ
|
|
|
Post by kenwig0556 on Mar 15, 2011 5:47:33 GMT
I was also going to mention this as my No. needle is from the No. 2 Nav and the No. 2 needle (double needle) indicates the No. 1 Nav. Any way to correct this in the cgf. ile? Thanks, lr. It wouldn't be correctable in the config file. Ken Mitchell's RMI is XML - as are the rest of his L1011 gauges - so it could be edited (simply switch the command lines around) with a proper XML editor.
|
|
|
Post by Dan K. Hansen on Mar 15, 2011 8:21:52 GMT
Like notepad ... I'll look into it
|
|
|
Post by Dan K. Hansen on Mar 15, 2011 9:44:35 GMT
Well RMI_Needle1 (the double) is connected to NAV1 and RMI_Needle2 (the single/sippled) is connected to NAV2 in the XML .... so the panel works as coded at least ... and that is both in the standard and the tape version of the panel ... But if standard is the other way around, I will have to to some corrections .... but I would have to look into some references in order to see which way around it was in the L1011....
|
|
|
Post by Dan K. Hansen on Mar 15, 2011 10:16:35 GMT
OK, corrected, and I will update the L1011 core panel files with the next update.
|
|
|
Post by aerofoto - HJG Admin on Mar 15, 2011 20:59:47 GMT
Thank you Dan ! Mark C AKL/NZ
|
|
|
Post by louross on Mar 15, 2011 21:50:47 GMT
That's just great! Thanks a lot, guys. lr.
|
|
|
Post by anderscn on Mar 16, 2011 3:23:55 GMT
Thanks a lot for the fast response A small issue really, that I easily could have lived with. Just asked mostly out of curiosity. The INS thing I havent´t solved fully yet - may look closer into the manuals. Best Regards, Anders
|
|
|
Post by anderscn on Mar 16, 2011 19:16:12 GMT
I found out about the INS stuff. Partly my own fault If for instance flying on the the leg 7-8, press WPT CHG followed by 0, 8 and then press INSERT again. Since WPT 0 always is the current position, leg 0-8 will now be the leg from the point when you press Insert, to WPT 8. Now the WPT´s from 1 to 7 can be intserted the same way as on the ground; press INSERT, then the coordinates and then INSERT again. It was here I overlooked something; On the ground when the MSU is in STBY position, the INSERT botton lights up when pressed. I doesn´t in the NAV position during flight. But never mind, just continue to type in the next coordinates starting with WPT 1 (not 0), it appears on the display as normal when typing in coordinates. And after leg 8-9 is finished, it will proceed to leg 9-1, etc. Best Regards, Anders
|
|
|
Post by CORLL ONE on Apr 19, 2014 11:07:23 GMT
Well RMI_Needle1 (the double) is connected to NAV1 and RMI_Needle2 (the single/sippled) is connected to NAV2 in the XML .... so the panel works as coded at least ... and that is both in the standard and the tape version of the panel ... But if standard is the other way around, I will have to to some corrections .... but I would have to look into some references in order to see which way around it was in the L1011....
|
|
|
Post by CORLL ONE on Apr 19, 2014 11:13:13 GMT
I'm seeing the above again with the latest L-1011 update. Sorry, not too swift with the cut n pasting of someone else's post. If I'm incorrect (highly probable) I apologize, I know you guys go above and beyond to make this all happen.
|
|
|
Post by aerofoto - HJG Admin on Apr 19, 2014 19:17:47 GMT
"IF" I understand you correctly ....
You're saying, that by default, the single lined needle points at NAV 2 whereas it should point at NAV 1 .... and the double lined needle points at NAV 1 whereas it should point at NAV 2 (other than this they're both working fine) .... is that correct ?
"IF SO" .... then it seems the original "minor error" (in respect of the programing these 2 needles for VOR navigation) might have been "inocently" replicated .... and in which case a gauges/core files edit will be required in order to correct this .... only I'm not sure how quickly this might be addressed.
Mark C AKL/NZ
|
|