JaimeC
-
Posts
22 -
Joined
-
Last visited
-
Days Won
2
1 Follower
JaimeC's Achievements
Newbie (1/14)
3
Reputation
-
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.
-
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.
-
Take Command! IXEG 737 Classic v1.21 Update Released!
JaimeC replied to Cameron's topic in General Discussion
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 -
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
-
Blank N1, N2, EGT on Engine Start
JaimeC replied to Greaser's topic in 737-300 Aircraft Systems and Operation
-
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
-
I just saw what's happening to more people
-
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
-
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
-
JaimeC changed their profile photo
-
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
-
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.
-
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.
-
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
-
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.
