Jump to content

PilotNuts

Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by PilotNuts

  1. Hello Poodster and Jan,

    Thank you guys for the response!

    1. For the first one, you are a genius! I do have an axis set to control the tiller; I find it more realistic when taxing, so I really hope IXEG can have a solution for this. 
    2. You are right again! I tried in HDG mode, and the bank limiter did work!
    3. I will try to make a video so it is more clear to understand. Also I found out that not only ground service window that will stop CDU from updating display, but all IXEG menu and windows. More over, they not only stop CDU's display but all display including PFD and ND. I will try to include this in a video too.
    4. My rendering settings are very low so Vram is really not an issue for me. I attached two pictures below to show this:

    As you can see there's a blue bar on the left side of ND:

    Screen Shot 2017-01-20 at 1.41.17 PM.png

    The color bar also appears in the preview when changing ND mode:

    Screen Shot 2017-01-20 at 1.41.49 PM.png

    I really appreciate all the help! And I'll be here if you guys have more questions!

  2. I don't know if any body has already reported these or they maybe already fixed by now, just let you awesome guys know:P

    1. The push back turn doesn't work for me. It just pushed straight no matter what direction I chose. I remember In some previous version it worked, but with either XP update or 737 update it stopped working some how.
    2. The bank limiter seems doesn't limit the bank angle.
    3. The CDU screen will not update the content if the ground service window is open. After you close the window, all changes in the CDU will show up.
    4. ND on the FO side has a narrow color bar on the left side. This problem is always there since the purchase on day 1. May be it is related to my software/hardware configurations since I know not a lot of people has this problem.

    Those are all I have for now. I'm using 737 V1.0.7, macOS Sierra 10.12.2, 16GB memory and AMD Radeon HD 6750M 1024 MB. If you guys have any questions about the problem I found, please let me know so I can let you know more. I'm here to help you guys to make this perfect product even more perfect!:wub:

  3. Thanks for the update! However the Mac installer doesn't seem to work under macOS Sierra. The zip package unzips fine, but when I try to install this window pops up:

    Screen Shot 2016-09-11 at 8.17.00 PM.png

    I have downloaded twice and both have the same issue. I'm afraid of using up the downloads so I didn't use the last download. Is there anybody else having this issue?

    Thanks for the help.

  4. To celebrate the upcoming release of IXEG 737 Classics, I opened up one of my earliest downloaded aircraft back in I was using XP9: the XPFW 737-300, just wanted to start to have some feeling of the 737 Classics again. To my surprise, I found this:

    B737-300_v9_beta2.jpg

    Look at those little words on the bottom of the picture... It's our dear @Morten and @tkyler!

    I wonder if there's any connection between this and IXEG 737 Classics...

    Anyway, let's all enjoy this upcoming weekend!:P

    • Upvote 2
  5. from http://developer.x-plane.com/?article=obj8-file-format-specification
     

    ATTR_LOD <near> <far>
    LOD indicates the beginning of a new LOD, which should be used to represent the object when the viewer is between near (inclusive) and far (exclusive) meters.


    Above is for *.obj file. If you use *.for, try

    http://developer.x-plane.com/?article=forest-for-file-format-specification
     

    LOD <max lod>
    This defines the farthest distance the trees can be seen. Lower values cause forests to disappear faster but result in faster frame rate.

    • Upvote 1
  6. Jiggy is correct.

    We chose the 430 purely for its size.  We did plan on the 530, but things got pretty crowded on the panel very quickly.

    I sincerely hope we can have an option to choose from 430 and 530. Personally I prefer 530 because of the bigger screen. I hope you guys could consider this. Anyway, a must buy aircraft!

  7. Scroll wheel support is very much appreciated. Thanks for implementing that.

    My only worry is that "hotspots" are getting too small when offering 2 methods (=2x2 hotspots + 3 clickspots on a very small area). If looking from pilots "normal" position it might be very difficult to find the right one. I think I would prefer an option to use either scrollwhell or click and drag/click and hold functionality - but have larger hotspots instead.

     

    But hey, there is also the new great 2D popup :)

     

    Regards

    Flo

     

    Good point. Especially if someone using TrackIR or Headshake plugin, your cursor can easily move out of the scroll wheel zone. I suggest we can select either methods from a menu, so we can have a relatively larger tolerance zone.

×
×
  • Create New...