Osu was unable to obtain a graphics context как исправить
Обновлено: 02.07.2024
This article is designed to give you the basics in troubleshooting osu!mac issues. It contains information on how to generate a report, troubleshooting techniques specific to Wine, and tips for communicating with other people in the osu!mac community.
Generating a report with osu!macOS Agent¶
To generate a report with Technocoder’s osu!macOS Agent:
Open osu!macOS Agent (duh)
Click the Troubleshoot report
Click Scan
Upon completion of the scan, click Copy Report
Save this to a text file or someplace where you won’t forget
osu!macOS Agent is a useful program every osu-stable player under Wine should have!
Generating logs for Wineskin¶
If your Wineskin isn’t starting or working properly, you can try diagnosing the issue with a Test Run of your Wineskin, that will produce logs that will describe any problems in detail.
To generate a Wineskin log:
Open the Wineskin program by following these instructions
Click the Advanced tab
Click the Test Run button
If osu! starts, you can close the program immediately (unless you need to test an issue that occurs at a particular moment in time, like when editing beatmaps)
A window like the one below will appear. Click Yes
Two plain-text files will appear. One contains information about your system and Wineskin, while the other provides a log of errors, warnings and events that were recorded while your Wineskin was operating.
Communicating your issues with other people¶
We want to help you get osu! running on your macOS-powered device, so to make the process as easy as possible for everyone involved, it’s important to be clear and concise right from the get-go.
Please do:
Work through the First steps section before posting for help
See the Common issues section to see if there’s a fix you can try
Describe your issue in lots and lots of detail
You can make a distinction between expected behaviour (what you think is supposed to happen) and actual behaviour (what actually ends up happening) in your issue report
Provide information on when/why your issue happens (if you know)
Provide information about your computer specs and the wrapper you used
Attach screenshots and log files (from both osu!macOS Agent and Wineskin
Tell us what you’ve already tried to do
The best place to report issues is on the osu! forums and the osu! for macOS support thread - make sure you put macOS in the title of your post (so other people know ofc).
Built with Sphinx using a theme provided by Read the Docs.
Visit more community resources to help you get osu! running on macOS.
View our Issues section for tips on how to troubleshoot your problems, or see how to diagnose common issues other users have experienced in the past.
The engine was unable to create a suitable graphics context.
Please make sure your graphics hardware meets the minimum requirements.
If you're running in windowed mode for the first time and you see
this message,
make sure your desktop color depth is set to 32-bit color.
Что делать?
Помогите
во 1 видюха похоже не тянет, обнови дрова на самые свежие, во вторых последняя строка 32 бита, прав кнопкой по раб столу, там параметры качество цветопередачи выставь 32 бита, перезагрузи и попробуй игру
Герман Колодезников запись закреплена
Зависание которое произошло, было из-за скина. Звук багается и приходится ребутать комп. Фиксанул зависание путем удалени9 всех хитсаундов скина
могу сказать сразу что тут будет быстрее винду переустановить чем искать решение проблемы
Resolution¶
Find your user profile/configuration file.
Locate where osu!.app (your Wineskin) is installed
Right click on it and select Show Package Contents
You should now see three files/folders: Contents , drive_c and Wineskin . Click drive_c .
From here, click osu! .
From here, locate osu!.yourcomputername.cfg and open this file in a plain text editor such as TextEdit.
For example, my configuration file is osu!.Adrian.cfg and it looks like this:
The default name for this file is usually osu!.Apple.cfg
Don’t get confused with osu!.cfg which is a completely different and much smaller configuration file.
Heed the warning and don’t share this configuration file with anyone else, not even us. It contains hashed versions of your passwords.
You’ll need to either delete or change a number of screen resolution options if you don’t know which is causing osu! to crash. If you know what option is breaking osu!, then you only need to modify/delete that specific option, as listed below.
Compatibility Mode¶
If you enabled Compatibility Mode and now osu! won’t start, find the CompatibilityContext option.
Use Command + F in TextEdit to quickly search for CompatibilityContext .
osu!macOS Agent will automatically disable Compatibility Mode as part of its troubleshooting steps.
If you did enable it, it would look like this:
If you can’t find CompatibilityContext ¶
Add the following line to the bottom of osu!.yourcomputername.cfg :
Screen Resolution¶
If you changed the screen resolution to something a bit weird, find these options:
Use Command + F in TextEdit to quickly search for these options.
Then, change the values accordingly to your last known previous settings, or to the recommended values as shown below. You can also delete them to have osu! initialise everything for you again.
Height and Width should be Wine’s specified screen resolution (or otherwise, a standard screen resolution like 1920x1080 )
HeightFullscreen and WidthFullscreen should be your computer’s effective/scaled screen resolution.
Find Wine's specified screen resolution
If you’re using Virtual Desktop on the X11 driver and need to modify Height and Width :
Locate where osu!.app (your Wineskin) is installed
Right click on it and select Show Package Contents
You should now see three files/folders: Contents , drive_c and Wineskin . Click Wineskin .
Click Set Screen Options
Locate the Screen Resolution dropdown as shown below - what it is set to is Wine’s specified screen resolution:
In this example it is 1920x1080 . Therefore, Width = 1920 and Height = 1080 .
Find your fullscreen resolution
To find osu!'s fullscreen resolution, you need to know your current scaled resolution for the monitor you're playing osu! on.
Now, replace the corresponding Height and Width values in osu!.yourcomputername.cfg with those displayed above.
Additional troubleshooting¶
Here are some additional troubleshooting tips that might help you diagnose and fix any issues you’re experiencing.
Accessing the insides of your Wineskin¶
Generally speaking, you can access the Package Contents of your Wineskin by right clicking on osu!.app and selecting Show Package Contents.
Three items should now appear:
Contents is a directory that Wineskin uses to store all its files - generally you won’t need to access this folder for troubleshooting
drive_c_ is an alias (shortcut) that represents a Windows filesystem which Wine imitates
Wineskin is the program you use to manage, edit, and troubleshoot your Wineskin
Locating osu! crash logs¶
Just like on Windows, osu! will generate it’s own crash logs that can be useful for troubleshooting.
If a dialog like the one below appears:
Click on the window. You should be able to view the crash logs now:
You can also find more logs under the Logs folder in your drive_c directory. To do this:
Locate where osu!.app is installed
Right click on it and select Show Package Contents
You should now see three files/folders: Contents , drive_c and Wineskin . Click drive_c
Your log files should be present here.
If that didn’t work¶
There could be something else going on here, and performing basic troubleshooting should help you get to the bottom of it.
If you’re not sure what’s going on here, copy any osu! crash logs as well as generating a report with osu!macOS Agent, and let us know on the forums.
Random side note that may or may not be useful to you: (i didn’t have anywhere else to put it)
Built with Sphinx using a theme provided by Read the Docs.
Visit more community resources to help you get osu! running on macOS.
View our Issues section for tips on how to troubleshoot your problems, or see how to diagnose common issues other users have experienced in the past.
Cause¶
This usually occurs because a user enabled Compatibility Mode in osu! settings, or changed to a screen resolution that Wine couldn’t handle.
Wine doesn’t support Compatibility Mode (aka osu!fallback) since it relies on OpenGL, whereas standard osu! uses DirectX. If you look in the logs, you may notice that osu! will be unable to find an OpenGL file.
If you need to use Compatibility Mode, you can try switching to the X11 driver, though in our own testing this made no observeable difference.
osu! was unable to obtain a graphics context¶
osu! crashes on startup, displaying an error message that says osu! was unable to obtain a graphics context.
First steps¶
To help us understand your issue a bit better, please perform the following initial troubleshooting & diagnostic steps as listed below. You can use this information to diagnose an issue yourself, or to request support on the forums.
Step 1: See Common Issues¶
Many issues already have solutions available to them. Check out the installation guide, Common Issue section on osu!mac and the outdated troubleshooting guide.
Here are some common ones we’ve been experiencing recently.
Step 2: Report and repair using osu!macOS Agent¶
Download the latest version of Technocoder’s osu!macOS Agent - older versions may have incompatibilities or bugs, especially with newer wrappers.
Once it finishes downloading, open osu!macOS Agent.
If you haven’t already done so, click the Select button and browse to osu!.app's location. The text box should display its filepath (e.g
/Users/firefly/Desktop/osu!.app ) and Wine Engine (e.g WS11WineCX64Bit19.0.1-1 )
Select the Troubleshoot tab, then click Scan.
After the scan completes, click Repair.
If this doesn’t fix your issue, click Copy Report. Copy the contents into a reply to this thread and we’ll do our best to help you out! Please don’t forget to do a Test Run as outlined in the next step.
osu!macOS Agent is a useful program every osu-stable player under Wine should have!
Step 3: Generating a Test Run through Wineskin¶
Locate your osu! installation.
Right click on it, then select Show Package Contents.
Open Wineskin.
Click Advanced.
Click Test Run. If osu! starts successfully (even with glitches), you can then close the program down.
Once osu! has either closed or crashed, a dialog will pop up asking you whether you want to view Test Run Logs. Click Yes.
Читайте также: