Jump to content

JaimeC

Members
 View Profile  See their activity

  • Posts

    22

  • Joined

  • Last visited

  • Days Won

    2

 Content Type 

Everything posted by JaimeC

  1. JaimeC
    Hi Ben, thanks for your reply . I clarify my specific situation. The problem with AI aircraft was a long time ago, this time I have not tried only with native AI. In fact, this problem was solved a long time ago, although later I had some more problem when I wanted to use AI and did not do any more tests. I just thought that the XP AI planes were wrong. But if there seems to be any type of conflict between Gizmo and AI planes (or maybe another common architecture, I don't know). See for example I am not stating with absolute certainty that that this problem is related to the problem of 737, but for my CTD it is certainly caused by Traffic Global + Gizmo and with both aircrafts. And if I'm not mistaken, both use Gizmo. By the way, Ben, I suppose it is better to install 737 and then the TBM or does the order not matter? Is it supposed that if I install TBM in the last place I have the latest version of gizmo? Is there a newer version? On the other hand, it seems that this problem has returned, I have not had time to review if it only happens with Traffic Global. In any case, i'm very happy to fly the 737 and the tbm900, although the skies are a bit empty ;-) If you need more data or tests, do not hesitate to ask me, I will try to help as much as I can.
  2. JaimeC
    I have also had problems in the past and, in my case, these are always related in some way to AI aircraft. Finally I ended up deactivating the native AI of Xplane. However, I recently bought Traffic Global to try and then the problems started again. CTD almost constant with the IXEG737 and the TBM900. I decided to make a clean installation and I have determined without a doubt (again in my case) that the problem is that Gizmo has problems with any type of AI plane. Deactivating Gizmo or deactivating anything related to AI, everything returns to normal. In my case obviously I prefer to fly the 737 and the TBM, so I have deactivated (sine die?) Traffic Global. I hope that one day this will be solved, it's a shame to lose the traffic (and the money ;-)) Sorry for my English, I know it's horrible.
  3. JaimeC
    The bug is solved !!!! Tests: Run X-Plane 11.20vr3 Load default C172 Load IXEG -> OK Load FF320 Load IXEG -> OK Load Aerobask Panthera Load IXEG -> OK All tests without restarting XP Great job @Ben Russell I send you some beers Make a backup of the previous one in another place. Remove the old Gizmo in XP and replace it with the new one. Do not copy over the old gizmo
  4. JaimeC

    Sorry, I did not realize I was writing in the feed instead of PM

  5. JaimeC

    Hi Cameron

    First of all I want to apologize for my bad English.

    I thought it more convenient to write to you privately so as not to flood the forum with similar reports.

    I just checked that if I load any plane first, including the default LR, I have the same error I mentioned in 

    For me it is not a problem, I just load the IXEG in the first place, but I wanted to inform you about it.

    As it is something that I have tried several times and I can reproduce it whenever I want, if you need logs or any other information let me know. I will be happy to help.

    Greetings

  6. JaimeC
  7. JaimeC
    I understand that things are moving continuously and very fast. No complaint on my part. If indeed that is the problem I will wait for the update or the patch. Unfortunately I can not return to the previous XPlane version because I just ordered my Oculus Rift. I do not plan to use it in complex aircraft like the IXEG, I do not think it is possible to handle it reasonably well by resolution issues, etc. but I want to test it in general aviation. Thanks again Ben, great support. PS: If you need any more data or any test let me know
  8. JaimeC
    I just saw what's happening to more people
  9. JaimeC
    Thanks Ben So it seems like a problem on my part? I have been flying for months and I have not had a single problem. Only yesterday, when I realized this issue, I decided to try reinstalling it. The funny thing is that it seems to have coincided with the Xplane update. This is the structure of my folders, I do not see anything out of the ordinary. The xplane folder is on the desktop. Another fact is that I recently updated the 1713 navigraph cycle, but I think I've flown with it without issues and I do not think that's the reason. GizmoLog.txt
  10. JaimeC
    After updating to X-Plane 11.20vr1 I realized that the digits are not there. I do not have any VR hardware. In the attached log there are several errors related to VR (normal), but there is other that seems strange to me: 0: 01: 35.003 W / ACF_CONFIG: ACF Config data file for Aircraft / X-Aviation / IXEG 737 Classic / B733_config.txt is not valid! I know it's a beta and possibly Laminar has broken something, but I wanted to inform you and know if there is a solution without having to go back to the previous version. I tried to reinstall the IXEG 737 but the problem is still there. Log.txt
  11. JaimeC

    Hi, Jan.

    First of all, I apologize for my bad English. Complaints to Google; -)

    I just wanted to tell you about some tests I've done on the famous ILS 22 EDDC (IDRW)

    As you can see I have tried the default c172, giving some curious results but confirming what you say (I never questioned it).


    However, I've done some rapid tests with other planes (Aerobask, Flight Factory A320 Beta) and the frequency they show is 109.75
    Instead, JustFlight PA28 Arrow III works just like the C172.

    I haven't tried to follow the ILS for lack of time, but I'm sure tuning 109.75 won't work.

    It's just so you have more data, because I see that there's someone talking about other planes. It's not a complaint on my side.

    I have decided to write to you privately so as not to advertise other brands, I hope not to bother you.

    Regards

  12. JaimeC
    I found something funny, my apologies if I'm doing almost an offtopic. Here tuning the correct frequency for Xplane (old) 109.70 The ILS is tuned (see deflection) and identified as IDRW Here tuning any other 110.70 Naturally, it's not identified or tuned in. Here tuning the new frequency according to Cycle 1713: 109.75 Not tuned but identified as IDRW !!! In any case, it is clear what Jan said, even if we update the cycle, the valid frequency is the one indicated by Xplane.
  13. JaimeC
    Interesting. I didn't know that, Jan. Thank you You can see what Jan says in this snapshot: Airac cycle 1713 but ILS still 109.70 Note: Obviously the cycle is updated in both xplane and IXEG.
  14. JaimeC
    Something is wrong with some charts (or they have changed frequency recently) Here 190.75 http://vau.aero/navdb/chart/EDDC.pdf Here 190.70 http://apxp.info/airports/view/EDDC http://www.vacc-sag.org/airport/EDDC
  15. JaimeC
    Oh, I read blurry instead of faded. In any case, I think adjusting the antialiasing may help quite a bit. The first capture is with FXAA, the second is with 4xSSAA, no other changes. Well, I think the difference is remarkable. Click on the images to see better.
  16. JaimeC
    I suspect it's antialiasing. Try 4xSSAA, although this will decrease your framerate a little (or a lot) depending on your graphics card.
  17. JaimeC
    Very interesting, thanks @Tom Stian I see that in my capture sim/cockpit2/gauges/indicators/wind_speed_kts exactly matches the indication in the EHSI (obvious). Soooo, isn't a IXEG bug. Now it's clearer and ... now I'm more confused. Why is it so different and weird, almost always about a half? The direction of the wind does not seem to be the factor, because in both dataref sim/weather/ and sim/cockpit2/gauges/indicators the deg are almost equal. Mysteries of the X-Plane? I will contact the author of FS-FlightControl commenting on that other dataref. As I said, the air speed indicated on the screen in his program is another. It's clear to me that IXEG is reading the correct data ... but (I think) FS-FlightControl too, and that is not possible. Note: Apologies for the excess of emoticons, but it helps me overcome my insecurity with English and clarify the meaning of my sentences.
  18. JaimeC
    Has anyone noticed this? Am I interpreting something wrong? From X-Plane official DataRefs Sim / weather / wind_speed_kt float n kts> = 0 The wind speed at the plane's location. Sim / weather / wind_speed_kt [0] float and kts> = 0 The wind speed in knots. Sim / weather / wind_speed_kt [1] float and kts> = 0 The wind speed in knots. Sim / weather / wind_speed_kt [2] float and kts> = 0 The wind speed in knots. As I understand it, the wind speed in the EHSI should be 233/7 and not 231/13 I'm sorry if it sounds like I'm talking about "wingflex and the cabin lighting" . I am very happy with IXEG and I really enjoy your top level plane ... But I would like to know how to interpret the wind speed in the aircraft. I'm just a curious guy
  19. JaimeC
    First of all I want to apologize for my English. I hope not to cause any diplomatic problem. I recently bought FS-FlightControl and I have noticed that the wind speed indicated in the EHSI does not match the one indicated in FS-FlightControl. I have contacted the author of the program and in the end I have come to the conclusion that the wind speed indicated in the EHSI is incorrect. It seems that this indication is of the wind speed in the layer (METAR or manually) and not the actual one that is experiencing the aircraft. That is, the EHSI is reading dataref sim/weather/wind_speed_kt [0] when it should read sim/weather/wind_speed_kt Is it intentional for some reason or am I completely wrong? I have to say that my level of understanding of the systems of a 737 is between zero and nothing. Thanks in advance
×
×
  • Create New...