Quake champions код ошибки 103

The resurgence of classic fast paced shooters continues as Quake Champions hits Early Access on Steam! As with any big name modern title, especially in unfinished Early Access form, there are bugs, errors, and launch problems galore.

Below we cover the most common Quake Champions issues players have been reporting, from failure to launch to hanging and freezing and even being unable to connect to a server. With a little troubleshooting and elbow grease you should be back into team death matches in no time flat.

Looking for help besides getting the game to launch? If you’re having trouble getting that kill/death ratio to an acceptable level, check out our latest Quake Champions walkthroughs here:

Quake Champions Won’t Launch

This iteration of the classic FPS franchise requires a graphics card that supports DirectX 11 or higher in order to even load.

To check your currently installed version of DirectX, type Run in the search bar and hit Enter when the program appears at the top of the results list, then enter the phrase DxDiag in the text box and click OK.

The bottom of the report screen that appears will list your current DirectX version. If 11 or 12 is listed, head over to your graphics card’s manufacturer website to make sure your specific card actually supports version 11. If it doesn’t, that means its time for an upgrade.

Running the DirectX Diagnostic Tool

If you are up to date on DirectX and meet the video card requirements, right click Quake Champions in your Steam library and choose Properties and then navigate to the Local Files tab and click Browse Local Files.

Finding the Quake Champions Steam game folder

Quake Champions Freezes On Launch

This problem is most frequently caused if you already linked your Bethesda account to your Steam account before installing Quake Champions through Steam.

Close down the whole application and exit from Steam completely (including accessing the Task Manager through Ctrl+Alt+Delete and manually shutting down the process if necessary). When you boot it all back up, the game should stop hanging.

If that doesn’t resolve the problem, make sure you have uninstalled all the files you may already have on your computer from the previous Bethesda beta edition of the game before it hit Steam. After uninstalling, restart your computer and load up Steam again.

Finally, make sure to verify your install through Steam to make sure you aren’t missing any critical files. Right click the Quake Champions entry in your Steam Library, select Properties, navigate to the Local Files heading, and finally click Verify Integrity Of Game Files.

Quake Champions Error 107 / Error 1201

While lots of players have been getting this one intermittently, unfortunately there isn’t a fix to the error code.

Both codes indicate there’s a temporary server issue, either meaning something is down that shouldn’t be and the issue is already being worked on, or the game is currently in a maintenance window where the servers are purposefully offline for a short time.

All you can do with Error 107 or Error 1201 is to wait a while, restart Steam, and try again. For up-to-date info on whether server maintenance is currently underway, head over to the Quake Champions Twitter profile here.

Quake Champions server downtime notification

Are you having any other Quake Champions framerate, launch, or error code issues? Let us know in the comments and we’ll look for a solution to the problem so you can get back to fragging away!

error 1501 when launching through qclauncher #14

Since yesterday’s QC update, launching through Bethesda Launcher works, but if I launch with qclauncher like all real men do, it launches the game but after all the movies play I get error 1501:

Unlike the last time when downgrading helped, this time neither version 1.05 nor 1.04 work :/

I really hope you’re still interested enough to keep this project going!

(And thanks again for quick fix the last time!)

The text was updated successfully, but these errors were encountered:

We are unable to convert the task to an issue at this time. Please try again.

The issue was successfully created but we are unable to update the comment at this time.

There are multiple threads about this, but this is a gem: https://bethesda. net/community/post/1237495

Bethesda Customer Support Team telling people «this is a Windows problem, go bug Microsoft», even though this has been caused by their update for tens of people, and shows a cryptic Bethesda bug number that won’t tell Microsoft anything

So yeah, this may have to do with that UAC popup before every launch (asking to create a pipe?) Hope that’s some form of anti-cheat and not another spyware.

The question remains, is it possible to emulate that without Bethesda. net Launcher.

I’ve been gone a while; is there still interest in this?

Also, we hope you had a great time on your vacation from Quake and all!

So I just confirmed:

So hell yeah there’s still interest!

I retract my comment about a pipe, after actually reading that message, the pipe is completely unrelated.

This can be tested from the fp branch. It successfully allowed me to authenticate with QC without 1501; however, I’ve only tested it on one machine (mine). I’d be curious to know if it works for anyone else.

Random1984 commented Oct 17, 2018

Runs fine in Win7 x64.

Worked on my Windows 10. The invisible Beth Launcher restarts while the QCLauncher was (not responding) on the settings screen need at least a small splash saying «gathering data in progress, please stand by» Afterwards it just worked, that’s what I’m talking about!

My Linux fetish aside, people who get error 1501 on actual Windows 10 probably won’t benefit from this either, if we’re simply extracting that profile from BNL, and then QC expects something else for whatever reason?

(inb4 Steam noobs comment: yes, I know it works from Steam through Proton, but I don’t want to convert my main account into a Steam-only one)

Worked on my Windows 10. The invisible Beth Launcher restarts while the QCLauncher was (not responding) on the settings screen need at least a small splash saying «gathering data in progress, please stand by»

I’ve confirmed that on start, QC itself also calculates the hardware fingerprint, using the same FP calculation mechanism that BNL does, regardless of whether BNL is open. The values between Windows and Linux (and even between two Windows machines) will not be the same for various reasons, i. e. different hardware info returned from WMI—if Wine even supports it, HKLMSOFTWAREMicrosoftCryptographyMachineGuid values will be different, etc. Since getting qclauncher to work on Linux is non-standard behavior, I’ve messaged you on IRC of some possible approaches to getting it to work. It would be neat if one of them worked.

My Linux fetish aside, people who get error 1501 on actual Windows 10 probably won’t benefit from this either, if we’re simply extracting that profile from BNL, and then QC expects something else for whatever reason?

That’s interesting. I haven’t heard of non-qclauncher users getting error 1501. Not sure what’s going on there.