You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[BUG] - im using r2modman to mod ultrakill on ubuntu mate linux, and its asking me to select the installation folder for it, but its not letting me
#1404
Open
null-VOID-null opened this issue
Jul 29, 2024
· 0 comments
Description of the bug
in settings, when i scroll to "select ultrakill installation folder" and click on it it opens up the file manager, and the window is labled "select ultrakill executable", with the box in the lower right corner thats usually for selecting file types is just ultrakill, not a file type. but when i navigate to the folder, it doesnt show the file, just the other folders.
To Reproduce
Steps to reproduce the behavior:
Go to change ultrakill directory (it says to manually set it right below)
Click on it
navigate to the folder
theres just the other folders, the actual executable, or any other files, isnt there
screenshot:
there should be a grey icon with a gear labled "ultrakill" in that screen shot, but there isnt. (I have checked the actual folder, its there, it just doesnt show up when going to select it from r2modman)
The text was updated successfully, but these errors were encountered:
Description of the bug
in settings, when i scroll to "select ultrakill installation folder" and click on it it opens up the file manager, and the window is labled "select ultrakill executable", with the box in the lower right corner thats usually for selecting file types is just ultrakill, not a file type. but when i navigate to the folder, it doesnt show the file, just the other folders.
To Reproduce
Steps to reproduce the behavior:
screenshot:
there should be a grey icon with a gear labled "ultrakill" in that screen shot, but there isnt. (I have checked the actual folder, its there, it just doesnt show up when going to select it from r2modman)
The text was updated successfully, but these errors were encountered: