Hi flightskyc,

 

thanks for that report!

 

I doubt that setting the N1 limit to CRZ would change anything (while that IS a bug, it should switch to CRZ automatically). The N1 LIMIT only really determines the limit of the autothrottle when it goes to "full power", which is not the case in the oscillation bug.

 

I hope that we have found the cause with the relation to FSUIPC. We will need to verify this, and then I am sure we will work together to get it resolved... now to squash all the FMC crashes that still lurk.

 

Thanks again, Jan

 

Yeah, XUIPC is a must for external applications.

 

I was hoping this was going to be the cause of my FMC freezes whilst waiting for EXEC to be pressed after making changes to the route/altitude restrictions/speed restrictions, but unfortunately that one still happens for me. (I do have a report for that in the bug forum @ X-pilot).

Yeah, XUIPC is a must for external applications.

 

I was hoping this was going to be the cause of my FMC freezes whilst waiting for EXEC to be pressed after making changes to the route/altitude restrictions/speed restrictions, but unfortunately that one still happens for me. (I do have a report for that in the bug forum @ X-pilot).

I had that too.

 

Best workaround seemed to be to pause, dismiss the gizmo window, exec, then unpause. Made it slightly less difficult to get to the exec button.

Hmmm, the problem is after all just an incompatibility with a plugin....

 

I was finding it strange that the team didn't test some of the problems being mentioned. 

 

Well, it IS one of the most ubiquitous plugins around, so it really does make you wonder if there ever was a beta test. I'd love to see a single person that hasn't had a fairly in-your-face bug like CDU entries not working or Gizmo crashing. 

 

I'm sure the plane will end up being great (it's already great to be honest), but the issues it has make it hard to understand a release at this point. If this had been released by any other developer, people would be furious. I wouldn't dare mention this over on X-Pilot though. 

I installed FSUIPC on my computer (never knew it even existed, lol) - and had the same problems with the autopilot. I guess that confirms the culprit. I try to contact the author of FSUIPC, hopefully we can work it out, if not then we can probably make our code deal with the conflict. Not having FSUIPC compatible is not really an option.

 

If you have a gizmo-console warning message pop-up, consider the flight over. It´s a soft-crash that will effectively render the code useless. Please file a bug (with a debug output, if possible) according to the "bug reporting guide" contained in the documentation.

 

If you want to continue your flight, you need to "reboot" gizmo (bump right screen edge to bring up the gizmo-pop-out gui, then click the little lightning symbol). All entered data is lost, but you can re-enter it and continue your flight.

 

Jan

 

 

I'm sure the plane will end up being great (it's already great to be honest), but the issues it has make it hard to understand a release at this point. If this had been released by any other developer, people would be furious. I wouldn't dare mention this over on X-Pilot though. 

 

Hi Marius,

 

without getting into details, but our options where A: release now and fix bugs as fast as we can or B: release in an unknown amount of time (at least in a year, very possibly never). What would have been your choice?

 

Cheers, Jan

Hi Marius,

 

without getting into details, but our options where A: release now and fix bugs as fast as we can or B: release in an unknown amount of time (at least in a year, very possibly never). What would have been your choice?

 

Cheers, Jan

 

Jan, if these were the only two choices you've obviously made the right choice. I also don't want to start an argument. I understand that there is pressure to release (financial or otherwise) but that still doesn't invalidate people's impressions. When one of the biggest ambassadors for our hobby rage-quits in front of a few hundred people, there may be a problem that would have been worth delaying a few hours for (or rather reevaluating your method of beta testing).

 

Don't take this the wrong way. It wouldn't bother me this much if I didn't like the plane as much as I do.

Hi Marius,

 

I agree with you 100%.

 

Jan

The problem is not only the few bugs or whatever but also the server availability. There is no website, no forum and I cannot download the product, tried for 3 hours now. I unfortunately did not first make a backup of my install before I decided to try a fresh default install without using Navigraph data. And the x-aviation install wrappers are obstacle in this respect although I know they were used before I bought the product.

 

Anyway I will go back to flying my FF767 in the meantime

I installed FSUIPC on my computer (never knew it even existed, lol) - and had the same problems with the autopilot. I guess that confirms the culprit. I try to contact the author of FSUIPC, hopefully we can work it out, if not then we can probably make our code deal with the conflict. Not having FSUIPC compatible is not really an option.

 

If you have a gizmo-console warning message pop-up, consider the flight over. It´s a soft-crash that will effectively render the code useless. Please file a bug (with a debug output, if possible) according to the "bug reporting guide" contained in the documentation.

 

If you want to continue your flight, you need to "reboot" gizmo (bump right screen edge to bring up the gizmo-pop-out gui, then click the little lightning symbol). All entered data is lost, but you can re-enter it and continue your flight.

 

Jan

 

 

Good to see that you were able to replicate this! After completing a short hop this morning (without XUIPC) and with cooperative VNAV/VS/FL Change/Alt Hold, It's easy to see how much work has gone into this product! The smoothness is incredible and the immersion is unique, it's a fantastic plane to fly and It's really great to see how responsive and proactive your team is being with the initial issues .

 

I haven't had any soft-crashes yet, but I still cant fix the freezing before EXEC button press (as show in this video here: https://www.dropbox.com/s/v2zm2twxcbrh1gl/Freezing%20bug.mp4?dl=0) - have you encountered this, Jan?

 

Conrad

.... When one of the biggest ambassadors for our hobby rage-quits in front of a few hundred people, there may be a problem that would have been worth delaying a few hours for (or rather reevaluating your method of beta testing)....

 

 

 

Wait, what? I've totally missed that one. Who was that?

I'm at a total loss at the moment. For the fourth time I have had a crash to desktop, this time it was while I was programming a route into the FMC, but it happens randomally. First time was after take off on the first tutorial flight, and the second was en route during the Nice-Geneva flight. I've only managed to complete two flights so far. The log file reveals nothing (Just X-Plane has crashed and nothing Gizmo related). I've even disabled all other addons and scenery and I still get random crashes. I now it's hard to answer, but any ideas? Is there some sort of logging I can enable?

Wait, what? I've totally missed that one. Who was that?

 

I guess that was Belynz on his Twitch-Stream yesterday.

I'm at a total loss at the moment. For the fourth time I have had a crash to desktop, this time it was while I was programming a route into the FMC, but it happens randomally. First time was after take off on the first tutorial flight, and the second was en route during the Nice-Geneva flight. I've only managed to complete two flights so far. The log file reveals nothing (Just X-Plane has crashed and nothing Gizmo related). I've even disabled all other addons and scenery and I still get random crashes. I now it's hard to answer, but any ideas? Is there some sort of logging I can enable?

 

Might not be related but have you updated SkyMaxxPro to 3.1.2? I was getting CTDs with 3.1.1 which went away after update.

 

I guess that was Belynz on his Twitch-Stream yesterday.

 

I've had no real problems as yet other than the fact that the nice little view system they have implemented doesn't seem to work for me. I need XPUIPC to run a hardware radio stack so am loath to remove it but it's not a biggie anyway so I'll patiently wait for the various fixes to roll in as should others imo. It is after all v1.0, anyone who was expecting perfection was expecting too much though I do have sympathy for those who are having bigger problems than I.

 

 

Might not be related but have you updated SkyMaxxPro to 3.1.2? I was getting CTDs with 3.1.1 which went away after update.

 

Thanks no I haven't   , so will give that a go. It could be related to SMP as that's the only plugin I have enabled

without getting into details, but our options where A: release now and fix bugs as fast as we can or B: release in an unknown amount of time (at least in a year, very possibly never). What would have been your choice?

 

The product must be released some time. Nothing will ever be perfect on release day.

 

As long as the team don't "release and disappear", there's no problem at all. I think you guys are doing great

 

Hell, even software developers like Dassault release their CATIA full of bugs every year and they resolve them as they can... The difference is a license of CATIA costs in the order of 100.000 €

I installed FSUIPC

Juste to be clear its xuipc that your talking about right ...

you could try to delete in the preference folder the autosave.

That messed some aircraft before ...