bigbasspic

Will do if I run into trouble – though me only shooting with my Nikons... Thx, Jan! Bassy regards Benjamin

Hmmm... This machine works quite well in current state for all the stuff I really need it for... Before going down this road – never change a running system! – I could mount the disc on another machine with newest OSX and have a go on it. Is the IXEG activation bound to my computer like eg the network card or can I try this without hassle? Thanks again, Jan! Bassy regards Benjamin P.S.: Did read the threads, thanks a lot...

Here we are. Vid attached, but – as expected – it is "time-compressed" too, as XP doesn't write the vid file while too busy updating the plane. But if you step through at ~6 sec. you see the effect shortly, it took about one minute real time. After this you see all the clicks that I did on the EXEC-button ,-) Did forget to do the debug '....' on the FMC, grmpf. The MBP is quite under load when flying XP, next up may be a cooling device, but as said it doesn't affect me flying in other planes with current settings as it does when I try to do the "direct to". Bassy regards Benjamin B733_1.mov

Will do this, Jan. Never been at TXKF ,-) Just to confirm: When to do the MOD thing? In the climb, on cruize alt, after a certain time, when approaching the first waypoint??? Sitting at TXKF with ~38 frames in captains view and ~42 in outside view (shift-8). (no buildings in scenery, just runways, papis and runwaylights.) No virus scanner, just a firewall (Little Snitch). OS 10.9.5, latest of the 10.5. branch. Does not give any problems using xplane with other planes. P.S.: Just to let you know: The plane is - apart from this bug - very gentle on frames on my schlepptop, in the 30s normally. Bassy regards Benjamin

Thanks xplana!

Removing XSquakbox does not solve the problem. Where do I find the IXEG debug text that some users do post here? Benjamin

Thanks, Jan. Will also try again without XSquakbox. Bassy regards Benjamin

Well, after my last rant I thought about gaining some positive IXEG karma points and give some more information about the – 1.0.3 still existing – problem over here, because this makes the plane unflyable for me on VATSIM. When (enroute) trying to skip some waypoints and go direct to another waypoint on the LEGS page, I can click on the desired point to bring it to the bottom left of the FMC. But when I try to insert this point into the first position of the legs, framerate drops immediately to around 0.3 – and the plane and me are lost in time tunnel ,-) If I continue looking at the FMC – and the spinning ball (mac) – after a long time (40 sec or more, it depends...) the new waypoint appears on the FMC and MOD is indicated, EXEC gets lit. IF (not always possible) I then manage to get the click on this button happening, everything is back to normal again. Looks like a too tight loop (doing the new calculation for the route?) to me, as a tail on the gizmo log gives constant updates on processing points, interceptions et al while the plane is unresponsive and XP does not process mouse clicks any more. If you need more information, let me know. MacBook Pro 15 Mid 2012, 2,6 i7, 16GB, SSD (system), 2TB HD (XP), OS 10.9.5 XP 10.45, plugs deactivated (see screenshot), XP log & Gizmo log attached. Bassy regards Benjamin GizmoLog.txt Log.txt

Ben, I KNEW it would be for nothing to add the GizmoLog.txt as I did. *as expected* Benjamin

I bought this plugin mainly because of the FMC. After some handflown patterns (beautiful!) I tried the simple route EDDW EDDH. The plane never reached its destination, because this gismo-CRAP crashed every time. All plugs disabled. But at least it got off the ground. After update 1.0.2. it crashes at the point I execute this really simple plan. GizmoLog.txt attached. No, I'm not going to make a video of this. After all the things IXEG said about their software prior to release I can only say this is RIDICULOUS. Being a programmer myself, I would be ashamed if I would sell software like this. Benjamin GizmoLog.txt

Thumbs up for storing the state of the beast ,-)

https://www.flightradar24.com/reg/n654sw

Yeah, should have announced the release time in UTC ,-)

Wise words.

Not necessarily from my side. I'll get them both @Cameron As you said, these are different beasts, and nobody is gonna get hurt anyway - apart from the cracks and scratches on the pavement after my first landings!

Guess the guys just wanted to be ahead of the x737 aka before 1st of may

So THIS is going to be a x-plane-spring-feast this year: IXEG and x737 being released soon! How cool can it get??? Vatsim / Ivao / Pilotedge will file more 737 flightplans than ever Bassy regards Benjamin

Copy that! Sorry, IXEG-Team. Keep on progging...

Sometimes I do enjoy the grumpy voice of some of the IXEG members in this forum.

Also called F-clef: https://en.wikipedia.org/wiki/Clef

On 2/26/2016 at 4:58 PM, Morten said:

Seems to be a step into no-man's-land, I would opt for the "That's a Rookie move: Expect the unexpected!" Just kidding... In case of "B", "C" and "E" I would expect the plane to act as laid out, case "A" feels wrong to me, in case of "D" I would not expect automatic climb after the "AT" or "Below" point – as this has to be cleared anyway, or was defined in the flightplan. So worst case would be flying on the "AtOrBelow" level till the T/D, then joining the descend. But as said, I am a Bass Player, not a pilot Bassy regards Benjamin

I guess it comes down to the question: How would the real thing handle this? Do it the same :-) Sorry Glad for being pragmatical, I am a Bass Player... ,-) Bassy regards Benjamin

Ah, good And I don't mind seeing them from outside, as I will be on the left seat in this plane anyway... Bassy regards Benjamin

My thoughts. As long as I can hide them, I don't care Bassy regards Benjamin