Jump to content

N1K380

Frozen-Inactivity
  • Content Count

    27
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by N1K380

  1. It is using the actual software from Garmin, would need to talk to Jeppesen and pretend you have a real 750. A single region is normally around $300 US/year. Worldwide is a cool $1000/year.
  2. Dden Challenger 300 Replaces the CDU, which is mirroring onto both sides. The function keys of the CDU are disabled, however I have not been able to find and edit the main clickspot. Clicking on the GTN triggers the default G430 😞 Download Link -- Side Note -- Jean-Luc any chance you could edit the OP to create an index of what aircraft mods are available in this thread?
  3. Hi, Trying to work my way through a few aircraft mods. Can anyone provide some input on replacing the default XP11 CDU? I'm not sure where it is hiding, can't find it in the panel.png so I'm at a bit of a loss as to where the gauge is actually being drawn from. Is it possible to bake a gauge into the cockpit.obj and map the texture to something other than the panel.png? The tutorials I have found are for outdated versions of both blender and the xp scripts so im slowly catching up with the modern versions ways. Ideally I would like to get to the point where I can remap the texture in that position to create a 750 rather than replace the screen. Baby steps 😉 Thanks Nick
  4. Thats the most random post I've ever seen in a forum 🤣
  5. Gotta find it first 😉 If only the blender import could bring in the animations and manips too, would be a walk in the park then...
  6. delete a line, save, test, if its the wrong one, ctrl + z, start again 😶 Not really any other way without knowing exactly what they called it.
  7. I meant the guage itself, if you look at the distance from the bottom of the compass the panel_preview appears to have far more than the gauge is showing in the screenshot. That's what i was trying to compensate for.
  8. I think your position is wrong, its hard left boarder so should be a 0, but at the same time I think its cropping that gauge into the avidyne. Give this a go: frame.rect = 100,1528,650,390 - kinda hard to pick the exact position with the crop. Would also suggest changing frame.type to PANELS instead of PANEL3D, I've had that fix it before where a custom gauge was being drawn on top of the GTN.
  9. I don’t have it, looks like there’s an MFD top centre of the panel? Could replace that with the GTN 750 screen potentially. If you can use the ‘make panel screenshot’ function of XP with the avionics all on, post the panel_preview file from the aircraft 3dcockpit > -panels- folder and I can send you the RXP code to test. No guarantees cos I can’t test it.
  10. That's only an excerpt of the file, did you replace just the corresponding section or the whole .ini file? The code looks right for that section.
  11. Outdated already 😛 Only had my macbook with me, which doesn't run GTN's. Code kept me busy on a few weeknights.. Just tested using two 750's so it should be working with the 650 now. Remapped the 3D panel buttons while i was at it. Files are in the aircraft mods thread
  12. Slowly getting my head around all this.. Aerobask Eclipse 550 I have remapped the Aerobask GTN bezel buttons to RXP so two versions.. GTN 750 and 650 https://www.dropbox.com/s/wzot352hf97oxrj/EA50 RXP 650 and 750.zip?dl=0 GTN 750 only https://www.dropbox.com/s/yi79x7hf7j0toa0/EA50 RXP 750.zip?dl=0
  13. If the RXP 750 turned up then this should fix it, if not I'll have time on the weekend to give it more time. Annoyingly I can't edit the previous post so ill try this method 🤔 https://www.dropbox.com/s/nw7mmtex4lq1bbx/RealityXP.GTN.ini?dl=0
  14. Still playing around with settings etc trying to get a desired result, think something is fighting the RXP data. Would editing out the 530_Screen gauge from the panel have any impact or is it happy sitting in the background of the GTN doing nothing?
  15. +1, did my head in with blender trying the same. Would love a tutorial of any kind if someone has the time.
  16. Give this a roll of the dice... GTN 750 is set as the primary and Nav 1, 650 on 2.
  17. Zarigani pretty sure I've seen it too, really wish the forum here was a bit more organised. ClayWagner, that baron example is relatively straight forward, a few videos on youtube too. Would be happy to give it a go if you want, but need a file from you so I know where it goes.. If you could go into keybindings and look for "Make screenshot of your panels", assign something then use it. Should create a "Panel_Preview" image file in the Eclipse 550 > cockpit_3D > -PANELS- folder. Just make sure the avionics are on when you do that and don't resize the file. I can't really test it, no guarantees I get it right first go 😉
  18. No update, only XP itself, and being steam based no reversion available. I'll keep playing around with it and see what happens.
  19. I have it in the Aerobask EA50 and its working ok. The problem child is the LES SF34. The Saab it seems to be completely ignoring the RXP data now, have had it in the 530 frame without issue up until now. Their support forum had another case of similar GPS lack of position problems with the default, response was "The 530 in the Saab is stock/default. If you truly believe something has changed in 11.30 you should file a bug with Laminar." Obviously using the RXP gauge I came here with it. The best I've worked out playing with all the settings is connecting it to the VOR1 indication, in which case it will track it but oscillates pretty bad. I did notice the same settings in the EA50 the PFD was solid, but the standby CDI was constantly flickering like it was fighting to be the dominant source. I can grab a video of it but won't be home till the weekend.
  20. @westman do you have the rest of that SF34 setting file? Since steam updated it to 11.30 on me the Saab seems to be ignoring the RXP nav data and drifting off on some random course when it's in LRN1 with no CDI indication. Would love to get a copy if yours is still working.
  21. I see. It was working fine before 11.30, had the GTN embedded in the VC in place of the 530. It just randomly stopped picking up the Nav inputs on me, try to engage it and the plane just goes off on some random direction. Just noticed the nav indications on the EHSI matched the 530 when I brought it back. Must be the EHSI dragging direct numbers or something then.
  22. hi, I am having a problem since 11.30 came out. Without RXP guage initialised the default 530 and subsequently aircraft operate normally. As soon as I add the GTN750 in, the default GPS reverts Speed and DTK to 0, CDI remains centered, default 530 looses all map icons and possibly its location but the distance is correct, meanwhile the course bar completely disappears from the CDI. The aircraft dev has said in a previous post that the aircraft just takes the native 530 outputs, I can only assume the RXP is doing odd stuff now. Slightly lost, tried deleting and reinitialising the rxp.ini file in the aircraft folder. Setting the 750 to not be the master device brings back all the info, but the CDI then reverts to the 530 indications and the auto update GPS waypoints option is not pushing the plan across to the 530. Version 2.5.11 Any suggestions?
  23. Hi, I am trying to emulate some of the panel configs which replace the 530 screen with the 750 in the 3D panel. How are you guys working out the correct position to use in the RXP ini file? I've opened up some of the defaults to play around in plane maker and found the position reported in there for the 530 screen does not correlate at all to the ini file. I.E. the default B58 530_Screen in the 3D Panel in plane maker is X:405 Y:315 The RXP .ini file from the panel mod config thread has it at X:275 Y:666 - where can I find those numbers for various aircraft without blindly changing them to see where it turns up? Is there a more in depth manual for this than the 16 page document that basically says there's an .ini file, good luck with that.... Thanks
  24. Hi, I like the view manager (shift+1), but I don't like the way it stole the F9-F12 default view change keys. Does anyone know a way to liberate the captive F keys whilst retaining the usability of the view manager? Thanks Nick
×
×
  • Create New...