xPilot Frame Rate Logic

[Andreas Fuchs]

Somebody will come up with a scrip to automatically re-connect

By the way, I ll fly elsewhere until xpilot just kick off only when it is mandatory to do that.

Try out swift. Have you?

[Daniel Dezulier]

I used a lot XSB 1.3.3

I tried xPilot

I'll try Swift

and also perhaps XSB 2.x except if they have installed a disconnection threshold.

[Nestor Perez]

ALL X-Plane compatible clients (xSquawkBox, xPilot and swift) will eventually have the automatic disconnection when the simulation rate is slow for too long integrated. At the moment of writing this post swift is the only option left for X-Plane without the automatic disconnect (I think), but sooner rather than later it will also have it.

 

Clients without the automatic disconnect feature implemented will not be able to connect to the network, so even if you can "run away" from it now, it will unfortunately stop being this way sooner rather than later. Of course, we will try to make sure that all the "buguettes" are fixed before making the move

[Andreas Fuchs]

At the moment of writing this post swift is the only option left for X-Plane without the automatic disconnect (I think), but sooner rather than later it will also have it.

Correct, but until implemented it will have been tested thoroughly to rule out game-breaking bugs.

[Andreas Fuchs]

I'll try Swift

To provide you with a smooth start, check out our tutorial videos. In the video details you'll find all necessary URLs as well.

 

[Justin Shannon]

You know people are going to reconnect anyways right away right? i was getting 50 fps when it disconnected me it dropped momentarily while going through clouds. btw but thats not the point. i actually only have had 2 disconnects since the changes. this needs to be resolved via education and not technical blocks. imho

 

People will of course reconnect anyway, and it's more than reasonable in the situation you just described while the logic is still being fixed. I'd normally agree that this should be an education issue but warnings had been issued for a while prior to this change - let's wait for the fixes, and see what happens next I think.

What fixes? I've already mentioned earlier in this thread that I will not be making any more changes to the time dilation/simulation rate detection (which is what it truly is) in order to keep it consistent with the other X-Plane clients (currently only XSB).

[Alexander Cohrs]

Even in case it turns out that people are disconnected also when above 20 fps or when they are below 20 fps just for very few seconds?

[Nestor Perez]

That has already been fixed in the last release. Just see how no new threads are appearing about it. Now it's just discussion about "what if"

[Andreas Fuchs]

What fixes? I've already mentioned earlier in this thread that I will not be making any more changes to the time dilation/simulation rate detection (which is what it truly is) in order to keep it consistent with the other X-Plane clients (currently only XSB).

And what if it transpires that the current fix is not good enough for practical use? I would abstain from so absolute comments until we have a sufficiently good sample of X-Plane pilots who do not suffer anymore more from unjustified disconnects or FPS-warnings.

[Alexander Cohrs]

Ah, then I misunderstood the latest posts from Daniel or John, sorry. Thought they still have these problems. If it turns out there are no more false disconnections at all, then disregard my last comment.

[Justin Shannon]

What fixes? I've already mentioned earlier in this thread that I will not be making any more changes to the time dilation/simulation rate detection (which is what it truly is) in order to keep it consistent with the other X-Plane clients (currently only XSB).

And what if it transpires that the current fix is not good enough for practical use? I would abstain from so absolute comments until we have a sufficiently good sample of X-Plane pilots who do not suffer anymore more from unjustified disconnects or FPS-warnings.

If something transpires, then I’ll address it then. However, XSB has been using the same code since 2.0 beta was released with very few complaints. I have no control over X-Plane and when it decides to slow down the simulation rate.

 

Also, if you want me to abstain from such comments, then let’s start by not hijacking threads telling the user to use a different pilot client.

[Michael Swannick 830306]

Hi Everyone,

 

Just getting back into VATSIM after an extended leave and I'm having some issues staying connected.

 

I run a server computer for my 737NG flight deck. This runs Xplane and VATSIM, I run five computers in total for the deck and have no issues there.

 

My Xplane/xPilot server computer is an I7 computer with an Nvidia 970 video board installed. ALL my sliders are "FULL LEFT" and are kept that way all the time. There is no demand on this computer at all. My frames are in the 80s solid, I do not run a V/C or 2D panel on this server computer either. Yet I get kicked for less than 20FPS.

 

It never happens on my server computer!!! I'm NEVER @20 fps, let alone for 30 seconds at a clip to get kicked. I hardly get that low on my three main visual displays, even they only dip into the upper 20s every now and then while in ORBX territory.

 

I was kicked three times last night, even while flying over water inbound to KMSY. Photo shows fluctuation between 74 and 80 FPS. My setup isn't doping from 80 fps to below 20fps over water at night.

 

I could use some help.

 

Thanks

 

[Michael Swannick 830306]

Hi,

 

This is the view from my three visual computers, they are locked at 30fps as are the monitors locked at 30MHz. They very rarely drop below 30fps. The demand in this video was far higher than when I was flying online last night. It was a smooth approach with my frams staying where they always stay, now my server computer runs at over twice the frame rates you are seeing here.

 

Am I missing something as far as a setting somehere inside XPilot?

 

 

Hi Everyone,

 

Just getting back into VATSIM after an extended leave and I'm having some issues staying connected.

 

I run a server computer for my 737NG flight deck. This runs Xplane and VATSIM, I run five computers in total for the deck and have no issues there.

 

My Xplane/xPilot server computer is an I7 computer with an Nvidia 970 video board installed. ALL my sliders are "FULL LEFT" and are kept that way all the time. There is no demand on this computer at all. My frames are in the 80s solid, I do not run a V/C or 2D panel on this server computer either. Yet I get kicked for less than 20FPS.

 

It never happens on my server computer!!! I'm NEVER @20 fps, let alone for 30 seconds at a clip to get kicked. I hardly get that low on my three main visual displays, even they only dip into the upper 20s every now and then while in ORBX territory.

 

I was kicked three times last night, even while flying over water inbound to KMSY. Photo shows fluctuation between 74 and 80 FPS. My setup isn't doping from 80 fps to below 20fps over water at night.

 

I could use some help.

 

Thanks

 

[Andreas Fuchs]

Hello Justin,

If something transpires, then I’ll address it then. However, XSB has been using the same code since 2.0 beta was released with very few complaints. I have no control over X-Plane and when it decides to slow down the simulation rate.

there you go. This statement is 100% the opposite of you have written before: "I will not be making any more changes to the time dilation/simulation rate detection". How can we be 100% sure that the current software version does not continue to kick people off the network, although they only suffer momentary drops of their frame-rates, which is not a problem. "I will not be making any more changes" sound very absolute, like "even if users continue having problems". This kind of communication upsets a lot of people here and on other forums. Me and other members have been defending the decision to force automatic logoffs of pilots with low fps, we have been defending your work and that you will surely be monitoring the situation and then improve the code, when necessary. How does that feel?

Also, if you want me to abstain from such comments, then let’s start by not hijacking threads telling the user to use a different pilot client.

I recommended to one single user to go and try another client, before he completely stops flying at VATSIM. Are you really interested in having people leave VATSIM? I am not.

[Justin Shannon]

Hello Justin,

If something transpires' date=' then I’ll address it then. However, XSB has been using the same code since 2.0 beta was released with very few complaints. I have no control over X-Plane and when it decides to slow down the simulation rate.[/quote']there you go. This statement is 100% the opposuite of you have written before: "I will not be making any more changes to the time dilation/simulation rate detection". How can we be 100% sure that the current software version does not continue to kick people off the network, although they only suffer momentary drops of their frame-rates, which is not a problem. "I will not be making any more changes" sound very absolute, like "even if users continue having problems". This kind of communication upsets a lot of people here and on other forums. Me and other members have been defending the decision to force automatic logoffs of pilots with low fps, we have been defending your work and that you will surely be monitoring the situation and then improve the code, when necessary. How does that feel?

Keyword is “if”. However, it has not transpired into anything more than a handful of users complaining because they’re getting disconnected because their simulator is incorrectly configured for their hardware. I have zero control over when X-Plane decides to slow the simulation rate.

 

As I’ve said previously, in version 1.1.9.0 I swapped out my original algorithm with the algorithm used in XSB. And since then, I have made changes to try to make the warning message less obtrusive, that is, not pop up the GUI window each time. If the day comes when XSB users begin revolting because of the change, then I will consult with Chris Collins and his team. Until then, the logic will remain how it is.

 

I recommended to one single user to go and try another client, before he completely stops flying at VATSIM. Are you really interested in having people leave VATSIM? I am not.

I’m all for a user trying a different pilot client if xPilot doesn’t work for them; however, this isn’t the first time you’ve hijacked a thread. I don’t go into the swift forums telling people to use xPilot instead of swift because feature Y doesn’t work. Common courtesy is all I’m asking here.

[Andreas Fuchs]

Hi Justin,

 

you are welcome to have a look around swift's Discord server. You will find us recommending xPilot to some pilots, because they want to have a condensed and simple client. There you go.

[Justin Shannon]

Alrighty, I think this is enough of this thread.