-
Content Count
9 -
Joined
-
Last visited
Community Reputation
3 NeutralAbout Ouroborus
-
Rank
RMS Freshman
-
xebuild is the commandline tool and xebuild gui is what it sounds like; the same tool but with a nice graphical interface!
-
Yes mine works and it also says so in the system settings. And regarding connectx I took the 2.2 connectx and put it in the plugins folder in F3 and that one autoloaded and worked like a charm as well.
-
Change your scan depth to a lower setting.
-
Delete all that in launch.ini and launch into F3 by default and you will see that it loads fine if you haven't touched anything. If not, do a cold boot ie power off completely one time.
-
No you don't need the path in launch.ini. Launch.ini is Dashlaunch's ini file not F3s. Start directly into F3 and the multidisc works.
-
There's your problem. It loads 2.2 multidisc plugin into memory or something, blocking F3 from loading it. Boot directly into F3 and the plugin will work!
-
Hi! I started my F3 through 2.2's file manager the first time and then scanned my content. Later on It came to my attention that the multidisc plugin wasn't loaded. Did as I used to do in 2.2 and cleared the data but it didn't clear the content but only the screenshots and covers. The database was still there. I don't trust the multidisc plugin without the initial scan and the plugin loaded. It's the failsafe way to go isn't it?
-
It's located in "data" folder in F3 folder and you can move your 2.2 folder into F3's TitleUpdate folder. A lot of folders here!
-
Are you starting directly into F3? Mine didn't work either until i put F3 as default in launch.ini and loaded it directly.