Jump to content
The Dark Mod Forums

Search the Community

Showing results for '"black screen"' in content posted in TDM Tech Support.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Discussion
    • News & Announcements
    • The Dark Mod
    • Fan Missions
    • Off-Topic
  • Feedback and Support
    • TDM Tech Support
    • DarkRadiant Feedback and Development
    • I want to Help
  • Editing and Design
    • TDM Editors Guild
    • Art Assets
    • Music & SFX

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. freyk

    No visual

    And If you cant see the console, during that black screen. Then you to create a log using start-arguments https://wiki.thedarkmod.com/index.php?title=Debugging_TDM_systemerrors And see the following topic:
  2. Quick update: Mission is now working, yeah I should had known, the problem was caused by a corrupted download. Looks like the mission files were not properly downloaded which caused the black screen glitch. I re-downloaded it and it fixed the problem right away. Thanks for the help, next time if this happens again for future FMs, I'll remember to re-download the mission again, sometimes a bad connection can cause missing files within the download itself.
  3. Ok, thanks for letting me know, so not necessary to use any of the dev build versions, just stuck to version 2.10 beta version 6. Yes, that's correct. I'm only able to get to the objective screen before starting the mission, but even the objective screen is also missing the script to describe the mission itself. It's just showing a blank sheet of paper without mission info. And then I click on "Objectives" and takes me to a black screen showing nothing, just hearing music/ambience sound in the background. I'm able to play the other FMs just fine without issues, "Down and out", "Written" and Hazard Pay. They all work fine except for "Iris" (Christmas Connections Contest)
  4. No you definitely have the right version then - just figured I would check since the dev builds appear above the beta builds in the downloader. Just confirming so I understand completely: you are able to select the mission and get through the briefing but at the point the objectives should display it cuts to a black screen? Do the custom assets up to that point seem to load correctly? Custom menu/briefing music, menu background/briefing, etc?
  5. Ok, here is my "darkmod.cfg" As for the "iris_is_black.txt" file, it's not there in my Dark Mod directory unfortunately. Weird, after opening the mission, I had to forcefully close the game because it would get stuck in the black screen and couldn't go back to the main menu. So, without it, hope this is enough to figure out part of the puzzle. Darkmod.cfg
  6. Yes, I did install version 2.10 beta version 6 and still got the problem with hearing music and ambience only, but stuck in a black screen. Should I install the latest "dev" build instead of using version 2.10 beta version 6?
  7. I just downloaded the latest beta version of the Dark Mod right now and by starting this specific FM: Iris, I get this black screen with the music and ambient sounds in the background, but no picture showing. I was only able to get to the mission briefing page showing the objectives of the mission and then by clicking on "Objectives" It takes me to a black screen. What is causing this issue? My other fan missions work just fine, I tested out other ones, so it's not my game. Could be this is a broken fan mission?
  8. I'm guessing this needs to be run in the windows command shell? In any case that's what I did. I only get a black screen with no music, left it for a while, clicked pressed alt+ctrl+², got nothing, no console, no map, no music, just a black screen. I decided to test a little further and started the game normaly, tried to launch the in-game console but it wouldn't appear neither. So I rolled back to the versions that worked and launched the command that you gave and it worked, on 2.07 the map launches but on 2.09 it does not. I even changed some of the cfg lines to check it out but no luck.
  9. Ok I tried what you said. I cannot generate a qconsole log with 2.09 or any of the test releases I tried. I tried test15973-8787 again. It doesnt run and I get the same problem. I tried test15973-8797. It doesn't even start, no black screen no music and mouse noises in the background, just a crash and I get a blue crash window with "error during initialization. too few!" written on top, whatever that means. I tried test16019-8980. Same problem as above with the too few thingy. Normal log says nothing usefull, no qconsole log. I went back to 2.07 to generate a qconsole log as I couldn't with the others. I couldn't get this release from the installer by the way as my antivirus blocks it saying it's a trojan and when it's disabled it shows, after a little while : ERROR: Missing chunk 51451011..40965251 (4284481536 bytes) after downloading URL http://mirror.mstrmnds.me/releases/zipsync/release/release207_from_release206/tdm_shared_stuff.zip Warning: Showing error message: Missing chunk 51451011..40965251 (4284481536 bytes) after downloading URL http://mirror.mstrmnds.me/releases/zipsync/release/release207_from_release206/tdm_shared_stuff.zip So I had to get this version from moddb. Other versions I tried download normally from the installer. Anyways I still got a few problems with 2.07, mainly that some textures are pink, but not all the time. For exemple in the training mission, the food plates in one of the rooms turn pink when I approach them while they are the normal gray color otherwise, same thing happens in other missions with these plates. There is some pink stuff above some doors too, and the FM "Coercion" has a big pink spot outside of a window. I believe this is visible in the qconsole log of 2.07 that I will attach here. I'm thinking this whole shit could be an Opengl error. I'm not sure my GPU is capable of running Opengl3.3 fully. It runs 3.1 I believe but I'm not entirely sure it runs 3.3 on windows 10. qconsole.logqconsole.log qconsole.log
  10. So I got back to my desktop and installed the dark mod 2.09a, but when I start it I get a gray screen for a couple of seconds then a black screen. I can hear the music and the menu sounds when I move my mouse but I can't see anything. I tried some things from what I could see in the forums but nothing worked. I have a pretty old GPU but it should run it no problem I believe (a Radeon hd 4850). Things i tried: -Downloading the latest dev build -Downloading the build test15973-8787 -changing glcore from 2 to 1 and to 0 -changing the resolution to 800x600 -starting it in compatibility mode windows 7 -changing glsl -changing shadow to 0 - downloading an executable posted by stgatilov in a post about the same problem (I can't find it anymore) None of this worked and the log file doesn't show any issues. Any idea how to fix this or if I need an older version, because I believe the GPU should be able to launch the game properly at least?
  11. Regarding 2.09 vs 2.09a / hotfix: Did you install TDM using tdm_installer.exe ? You can see whether you have 2.09a or 2.09 by looking at .zipsync/lastinstall.ini: [Version] version=release209a Or you can find line seta logFile "0" in darkmod.cfg and change it to seta logFile "1", then find qconsole.log and attach it here. It should contain engine revision number, which can be used to understand which version it is. Anyway, your problem will most likely happen both in 2.09 and 2.09a. Regarding the black screen problem. Most likely it is the same issue @freyk linked above. Especially since you confirm that test15973-8787 works properly. The current workaround for this problem is to set following in darkmod.cfg: seta r_glCoreProfile "0" After that 2.09a should work fine. Also, this problem is fixed on the latest dev build. But dev build are not recommended for normal playing: better use release2.09a with core profile fix. Also, I think we will release another hotfix for 2.09 (that would be 2.09b) somewhere in November. Specifically to fix this particular problem, and maybe something else. Make sure to install this second hotfix when it is released.
  12. OK Guys i thought id installed OK but at the end i got a compatability error and when i tryed to launch i got a black screen ! I then tryed to reinstall with compatability settings and the installer said i had installed successfully ! Tryed to launch and got the black screen again. I did a little search on the forums and it's looking like this might be a known problem. Is it a compatability issue with radeon drivers or am i missunderstanding the thread i read ? I have an Asus R9 270 which I hope is still good enough to run this game ! I used to be !! I alreao read about a hotfix but dont wish to do anything untill i get advice. Thanks got your help in advance.
  13. As far as I remember, TDM 2.09 requires OpenGL 3.3 to start. So either your OpenGL does not fit the requirement, or (as I guessed above) it has separate GL versions for core and deprecated profile. Perhaps version in core profile is newer than 3.3, but the version in deprecated profile is only 3.1 By the way, do you also have the problem with black screen in main menu and sound playing?
  14. I only have the default missions installed, the menu isn't visible at all. just a black screen with sound.
  15. @duzenkoTwo problems, first I did have my folders named darkmod in succession so I renamed to tdm and darkmod respectively. But the asset issue was fixed cause I forgot to run the flippin launcher... LOL So the engine boots up however... @stgatilovThe first time running, it decompressed textures but the game wouldn't start. Launched a second time and I get a fullscreen window, but it hangs on a black screen, last item in terminal is "Async thread started". When I run "thedarkmod.custom.debug" I get an ELF Exec error like it's compiled for wrong architecture, however a 'file' shows it is an aarch64 ARM executable. My terminal output below: EDIT: I noticed below the line "Unknown command '#'", I do know one project I was compiling on required me to modify a C file and change the # hashtags to // double forward slashes as ARM assembly uses // for comments. *Shrug* wooty@wootylx2k-ubn:~/build/tdm/darkmod$ ./thedarkmod.custom TDM 2.10/64 #9574 (1435:9574M) linux-aarch64 Aug 23 2021 01:34:57 failed parsing /proc/cpuinfo measured CPU frequency: 1000.1 MHz 1000 MHz unsupported CPU found interface lo - loopback found interface enx00249b1e62ae - 151.151.88.220/255.255.0.0 found interface virbr0 - 192.168.122.1/255.255.255.0 Found Unsupported CPU, features: TDM using Generic for SIMD processing. Found 0 new missions and 0 packages. ------ Initializing File System ------ Current search path: /home/wooty/build/tdm/darkmod/ /home/wooty/build/tdm/darkmod/tdm_textures_wood01.pk4 (376 files) /home/wooty/build/tdm/darkmod/tdm_textures_window01.pk4 (389 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_sculpted01.pk4 (463 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_natural01.pk4 (133 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_flat01.pk4 (302 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_cobblestones01.pk4 (224 files) /home/wooty/build/tdm/darkmod/tdm_textures_stone_brick01.pk4 (520 files) /home/wooty/build/tdm/darkmod/tdm_textures_sfx01.pk4 (69 files) /home/wooty/build/tdm/darkmod/tdm_textures_roof01.pk4 (72 files) /home/wooty/build/tdm/darkmod/tdm_textures_plaster01.pk4 (142 files) /home/wooty/build/tdm/darkmod/tdm_textures_paint_paper01.pk4 (63 files) /home/wooty/build/tdm/darkmod/tdm_textures_other01.pk4 (127 files) /home/wooty/build/tdm/darkmod/tdm_textures_nature01.pk4 (286 files) /home/wooty/build/tdm/darkmod/tdm_textures_metal01.pk4 (497 files) /home/wooty/build/tdm/darkmod/tdm_textures_glass01.pk4 (51 files) /home/wooty/build/tdm/darkmod/tdm_textures_fabric01.pk4 (43 files) /home/wooty/build/tdm/darkmod/tdm_textures_door01.pk4 (177 files) /home/wooty/build/tdm/darkmod/tdm_textures_decals01.pk4 (465 files) /home/wooty/build/tdm/darkmod/tdm_textures_carpet01.pk4 (92 files) /home/wooty/build/tdm/darkmod/tdm_textures_base01.pk4 (407 files) /home/wooty/build/tdm/darkmod/tdm_standalone.pk4 (4 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals_decls01.pk4 (27 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals07.pk4 (1111 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals06.pk4 (696 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals05.pk4 (119 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals04.pk4 (2869 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals03.pk4 (743 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals02.pk4 (1299 files) /home/wooty/build/tdm/darkmod/tdm_sound_vocals01.pk4 (82 files) /home/wooty/build/tdm/darkmod/tdm_sound_sfx02.pk4 (605 files) /home/wooty/build/tdm/darkmod/tdm_sound_sfx01.pk4 (966 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient_decls01.pk4 (8 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient03.pk4 (24 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient02.pk4 (163 files) /home/wooty/build/tdm/darkmod/tdm_sound_ambient01.pk4 (220 files) /home/wooty/build/tdm/darkmod/tdm_prefabs01.pk4 (961 files) /home/wooty/build/tdm/darkmod/tdm_player01.pk4 (125 files) /home/wooty/build/tdm/darkmod/tdm_models_decls01.pk4 (103 files) /home/wooty/build/tdm/darkmod/tdm_models02.pk4 (2053 files) /home/wooty/build/tdm/darkmod/tdm_models01.pk4 (3163 files) /home/wooty/build/tdm/darkmod/tdm_gui_credits01.pk4 (49 files) /home/wooty/build/tdm/darkmod/tdm_gui01.pk4 (721 files) /home/wooty/build/tdm/darkmod/tdm_fonts01.pk4 (696 files) /home/wooty/build/tdm/darkmod/tdm_env01.pk4 (152 files) /home/wooty/build/tdm/darkmod/tdm_defs01.pk4 (187 files) /home/wooty/build/tdm/darkmod/tdm_base01.pk4 (198 files) /home/wooty/build/tdm/darkmod/tdm_ai_steambots01.pk4 (24 files) /home/wooty/build/tdm/darkmod/tdm_ai_monsters_spiders01.pk4 (80 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_undead01.pk4 (55 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_townsfolk01.pk4 (104 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_pagans01.pk4 (10 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_nobles01.pk4 (48 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_mages01.pk4 (8 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_heads01.pk4 (100 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_guards01.pk4 (378 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_females01.pk4 (172 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_builders01.pk4 (91 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_beasts02.pk4 (229 files) /home/wooty/build/tdm/darkmod/tdm_ai_humanoid_beasts01.pk4 (23 files) /home/wooty/build/tdm/darkmod/tdm_ai_base01.pk4 (9 files) /home/wooty/build/tdm/darkmod/tdm_ai_animals01.pk4 (82 files) File System Initialized. -------------------------------------- Couldn't open journal files failed parsing /proc/cpuinfo alternative method used /proc/cpuinfo CPU processors: 16 /proc/cpuinfo CPU logical cores: 16 ----- Initializing Decls ----- ------------------------------ I18N: SetLanguage: 'english'. I18N: Found no character remapping for english. I18N: 1277 strings read from strings/english.lang I18N: 'strings/fm/english.lang' not found. Couldn't exec editor.cfg - file does not exist. execing default.cfg Unknown command '#' Couldn't exec autoexec.cfg - file does not exist. I18N: SetLanguage: 'english'. I18N: Found no character remapping for english. I18N: 1277 strings read from strings/english.lang I18N: 'strings/fm/english.lang' not found. ----- Initializing OpenAL ----- Setup OpenAL device and context [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1) OpenAL: found device 'SB Omni Surround 5.1 Analog Stereo' [ACTIVE] OpenAL: found device 'Kensington SD4700P Dual Video Dock Digital Stereo (IEC958)' [ALSOFT] (EE) Failed to set real-time priority for thread: Operation not permitted (1) OpenAL: device 'SB Omni Surround 5.1 Analog Stereo' opened successfully OpenAL: HRTF is available OpenAL vendor: OpenAL Community OpenAL renderer: OpenAL Soft OpenAL version: 1.1 ALSOFT 1.21.1 OpenAL: found EFX extension OpenAL: HRTF is enabled (reason: 1 = ALC_HRTF_ENABLED_SOFT) OpenAL: found 256 hardware voices ----- Initializing OpenGL ----- Initializing OpenGL display Borderless fullscreen - using current video mode for monitor 0: 3440 x 1440 ...initializing QGL ------- Input Initialization ------- ------------------------------------ OpenGL vendor: AMD OpenGL renderer: AMD Radeon (TM) Pro WX 4100 (POLARIS11, DRM 3.40.0, 5.11.0-31-generic, LLVM 12.0.1) OpenGL version: 4.6 (Core Profile) Mesa 21.3.0-devel (git-2b4b310 2021-08-21 hirsute-oibaf-ppa) core Checking required OpenGL features... v - using GL_VERSION_3_3 v - using GL_EXT_texture_compression_s3tc Checking optional OpenGL extensions... v - using GL_EXT_texture_filter_anisotropic maxTextureAnisotropy: 16.000000 v - using GL_ARB_stencil_texturing v - using GL_EXT_depth_bounds_test v - using GL_ARB_buffer_storage v - using GL_ARB_texture_storage v - using GL_ARB_multi_draw_indirect v - using GL_ARB_vertex_attrib_binding v - using GL_ARB_bindless_texture X - GL_ARB_compatibility not found v - using GL_KHR_debug Max active texture units in fragment shader: 32 Max combined texture units: 192 Max anti-aliasing samples: 8 Max geometry output vertices: 256 Max geometry output components: 4095 Max vertex attribs: 16 ---------- R_ReloadGLSLPrograms_f ----------- Linking GLSL program cubeMap ... Linking GLSL program bumpyEnvironment ... Linking GLSL program depthAlpha ... Linking GLSL program fog ... Linking GLSL program oldStage ... Linking GLSL program blend ... Linking GLSL program stencilshadow ... Linking GLSL program shadowMapA ... Linking GLSL program shadowMapN ... Linking GLSL program shadowMapNG ... Linking GLSL program ambientInteraction ... Linking GLSL program interactionStencil ... Linking GLSL program interactionShadowMaps ... Linking GLSL program interactionMultiLight ... Linking GLSL program frob ... Linking GLSL program soft_particle ... Linking GLSL program tonemap ... Linking GLSL program gaussian_blur ... --------------------------------- Font fonts/english/stone in size 12 not found, using size 24 instead. --------- Initializing Game ---------- The Dark Mod 2.10/64, linux-aarch64, code revision 9574 Build date: Aug 23 2021 Initializing event system ...852 event definitions Initializing class hierarchy ...172 classes, 1690368 bytes for event callbacks Initializing scripts ---------- Compile stats ---------- Memory usage: Strings: 45, 7160 bytes Statements: 20303, 812120 bytes Functions: 1278, 166124 bytes Variables: 91948 bytes Mem used: 2019680 bytes Static data: 3989840 bytes Allocated: 5034004 bytes Thread size: 7904 bytes Maximum object size: 884 Largest object type name: weapon_arrow ...6 aas types game initialized. -------------------------------------- Parsing material files Found 0 new missions and 0 packages. Found 3 mods in the FM folder. Parsed 0 mission declarations, no mission database file present. -------- Initializing Session -------- session initialized -------------------------------------- Font fonts/english/mason_glow in size 12 not found, using size 48 instead. Font fonts/english/mason_glow in size 24 not found, using size 48 instead. Font fonts/english/mason in size 12 not found, using size 48 instead. Font fonts/english/mason in size 24 not found, using size 48 instead. --- Common Initialization Complete --- WARNING: terminal type 'xterm-256color' is unknown. terminal support may not work correctly terminal support enabled ( use +set in_tty 0 to disabled ) pid: 4706 Async thread started Killed
  16. Wow, this is impressive I think crash on shader compilation is like getting internal compiler error from ordinary C++ compiler. Except that GLSL compiler is embedded, so consequences for crashing are much worse. Luckily, the problem can be worked around by simply removing the manylight shader. I think the black screen issue will return back to you after that By the way, do you want to go into the quest of reporting the issue to AMD? I recall I did it with the bug that texture fetches in global variable initializers didn't work, and got response like "upgrade GLSL version". At least that was response from someone from AMD, as far as I understood. Maybe a crash will get more attention. Also, it is very easy to debug if you attach a full crash dump...
  17. @Jedi_Wannabe, could you please check something about this issue? As written above, the problem depends on r_glCoreProfile cvar, which must be set in darkmod.cfg before starting TDM. We know that "r_glCoreProfile 2" does not work for you, but "r_glCoreProfile 0" does work. Does "r_glCoreProfile 1" work for you? Or you get black screen?
  18. Hi Thanks for the Dark Mod. Like other user i get a black screen with audio after executing "TheDarkModx64.exe" Version TDM 2.09. System Windows 7-64, latest updates. Custom install TDM Version "test15973-8778" works fine, so far Custom install TDM Version "test15973-8787" works fine, so far Custom install TDM Version "test15973-8793" --> black screen with audio Custom install TDM Version "test15973-8795" --> black screen with audio Custom install TDM Version "test15973-8797" --> black screen with audio Custom install TDM Version "test16019-8980" --> black screen with audio Custom install TDM Version "test16019-8981" --> black screen with audio Custom install TDM Version "test_release209_5542" --> black screen with audio ******************************************************************************* Setting r_glCoreProfile "0" in the file Darkmod.cfg is the solution that works for me! ******************************************************************************* Report with system images and log files: Thief - The Dark Mod BlackScreenSolution Regards elC Thief_-_The_Dark_Mod_BlackScreenSolution.zip
  19. If it were not compatible, you should be getting a black screen because nothing could be rendered without textures. But in practice, it does render, just with confused texture associations. It looks and feels very much like a bug, but unfortunately I don't (yet) have access to an AMD device myself, so it' very hard to debug...
  20. Addendum: if image_usePrecompressedTextures "0" -> BLACK SCREEN (game is working)
  21. Same problem (black screen on v2.09), same solution (setting r_glCoreProfile "0"). System specs:
  22. @id3839315 says the fourth script shows black screen, just like the first two. So the final decision is that "r_glCoreProfile 0" works fine, but "r_glCoreProfile 2" gives black screen. This may be some driver problem, e.g. some of the GL features previously hidden behind extension is not enabled by the problematic AMD driver under GL 3.3, while it should according to the specs. It is not just some function, because calling missing function would give immediate crash. Most likely some constant of mode. I think I have already ruled out: ARB_fence_sync ARB_buffer_storage (persistent mapping) ARB_bindless_texture (not used in menu anyway) ARB_draw_indirect (multi draw indirect --- not used in menu too) ARB_vertex_attrib_binding What else it can be? Maybe glDrawElementsBaseVertex (it was previously behind extension), maybe UBOs --- who knows. What can help here: Use deprecated profile --- I think this will serve as workaround. Request greater OpenGL version (e.g. 4.1 instead of 3.3) --- maybe it would help Hope that driver update would fix it.
  23. _apitrace_record3.cmd works, but 1 and 2 result in the black screen.
  24. Ok, I'll try to get some more information, but that would need more complicated steps from you. 1) Run tdm_installer without any custom checks, and make sure it installs release209 properly. Do not use test/dev versions for this! 2) Delete "currentfm.txt" file in TDM installation directory (if it exists). 3) Download apitrace from this link. It is a 7z archive with a folder inside. Unpack the contents of the folder into "C:\apitrace". Make sure that path "C:\apitrace\bin\apitrace.exe" indeed points to the executable! 4) Download attached zip file. Unpack its contents into the root of your TDM installation directory. Make sure you see files like "_apitrace_record1.cmd" in the same directory where you see "TheDarkModx64.exe". 5) Action time Run "_apitrace_record1.cmd". It will start TDM game, and after a bit of time you will hear music. Now press Ctrl+Alt+Tilde (~) to open console. Type "condump 1" and hit Enter. Then exit game by pressing Alt+F4. Note that you'll have to do it blind, so verify that both "1.txt" and "res1.trace" have been created in TDM directory. 6) Repeat point 5, but now run "_apitrace_record2.cmd" and execute "condump 2". 7) Repeat point 5, but now run "_apitrace_record3.cmd" and execute "condump 3". 8|) Take files "1.txt", "2.txt", "3.txt", "res1.trace", "res2.trace", "res3.trace" in TDM installation directory, and pack them all into 7z/zip archive. Upload the archive somewhere and share it for download. P.S. And if you start seeing the menu instead of black screen in any of the runs, of course report it 209_blackmenu_apitrace.zip
  25. I have the same problem too, and I also have a Radeon card. On Linux, however, instead of a black screen, it produces a bunch of colored artifacts obstructing view on the menu. I'll try both test versions and see the results1000
×
×
  • Create New...