Alt+tab to desk top then hit flight mode button, poof instant disconnect, literally takes about 2 seconds.
Any fixes for this Fdev?
Any fixes for this Fdev?
PvP Windows 10 allows for easy combat logging.
- Thread starter CMDR Rage Quit
- Start date
There was some talk of it being a karma hit in the upcoming changes, they'd need to identify false positives though.
Why should there be a fix for an intended OS or indeed hardware-level feature?
Taking a leaf off Fromsofts tree of DS games, great idea imo.
Quick, Frontier developers! Abuse some undocumented behaviour in the Windows API, manipulate an internal registry entry, or use any other arcane and unintended trickery to interfere with an OS feature! The customer demands it!
What's the 'flight mode button'? Do you mean the Flight Assist toggle? What do you have it assigned to?
If you think you found a bug that causes the game to crash, submit a bug report. There is a forum section for PCs here for the live game, or here for the current beta (3.0)
Combat Logging would be deliberately disconnecting or causing the game to crash.
If you are interested, there is a proposed solution for Combat Logging here, essentially it just puts you back into the same mode you left whether you CLog or accidentally disconnect. If you read the whole thread it will help you to understand both what it is and why it's an issue. If you think you can identify a flaw please post it up & someone (probably me) will try to help.
ftfy
that's easy, currently all combat logging seems to be considered false positive.
indeed not, but there could be a fix for a network not reacting properly to a peer blacking out.
He's talking about the button in the Windows UI that turns of all the wi-fi radios on the system.
It's really no faster to hit this than it is to deliberately disconnect by a dozen other means.
That's excellent news, if they are all false positives there is no problem with clogging at all.
Its not P2P. FD *could* implement a server side service to take over in the event of someone logging. This is because the game isn't 100% P2P, its a hybrid system.
Same as if it was a C/S architecture, if the devs don't implement a service to take over when someone logs then people would still be able to log.
The solution i have proposed on occasion, which doesn't impact people badly who are affected by random network dropouts or other non-intentional logs is simply to put in timeouts from Open.
First time, 1 hour lock out of open.
Second time, 1 day lock out of open.
Third time, 1 week lock out of open.
etc.
Numbers subject to adjustment, and there could be a decay over time, so like each month that passes without a log you drop back down a tier. Something like that.
That way only people who repeatedly log would find themselves locked out from open indefinitely.
Last edited:
gratulations
you seem to never have any issues with your network/hardware/OS/power/kids/pets/physics?
otherwise you wouldnt request to exclude ppl for S.H.
i am straight against CL,
but this is another example of a 1 dimensional view at things
With an unreliable connection on a bad day dropouts can happen a few times an hour, every couple of hours is normal even on a good day. I'd be perma-banned from open.
Thanks Morbad. So this is just a troll thread to stir up the pot then.
