CBBE doesn't work

[G4M3W1NN3R]

The problem is usually that people try to follow the instructions for a manual/NMM install while using Vortex or MO2.

 

If you don't actually follow directions, you won't get results.

 

Unfortunately, most people who report issues do so by saying "I did everything right, why doesn't it work?" instead of saying "this is a detailed list of what I did, with my load order list and some images of important folders/settings/error messages, what did I do wrong?"

 

Presuming you did everything right and that it "just doesn't work for mysterious reasons" instead of trying to figure out what you did wrong is not a very effective troubleshooting technique.

fair point

[Guest deleted34304850]

 

They don't use "virtual drives". They use symlinks. The files are all there on the same drive same as with NMM.

i thought the whole point of vortex was to be built on the same foundation as m02, thus virtual file system /drives, hence i was under the impression it also uses Virtual Drives/ file system

 

if thats the case why is it much more common to see CBBE issues with Vortex and or M02 vs NMM or manual Installation, baring in mind how long these have been available. i have seen far more reported issues with CBBE with Vortex/M02, vs the entire time of NMM

 

but ye il take your word for it that Vortex does not actually use Virtual Drives, and will likewise edit my original reply.

 

the issues arent specific to the mod manager thats being used, they're more likely to be down to the fact that the user thinks they are beyond reproach and have done everything perfectly. thats seldom the case.

[StormWolf01]

Not so much as what techs would refer to as virtual drives. While I dunno MO2, vortex installs to folders within it's own folder. To preserve the original game files, if my understanding is correct. And I'm more than welcome to receive correction on that, so please set me straight so that I understand it correctly.

TBH it's been so long since I "installed" CBBE, I don't even remember the process thru a manager. Tho manual placement of the files, or... especially in my case... REplacement of the files, is simple as pie, and works every time.

[G4M3W1NN3R]

Not so much as what techs would refer to as virtual drives. While I dunno MO2, vortex installs to folders within it's own folder. To preserve the original game files, if my understanding is correct. And I'm more than welcome to receive correction on that, so please set me straight so that I understand it correctly.

TBH it's been so long since I "installed" CBBE, I don't even remember the process thru a manager. Tho manual placement of the files, or... especially in my case... REplacement of the files, is simple as pie, and works every time.

 

true, i learnt of virtual drives a very long time ago (back when i was heavily into system building, learning how hardware interacts with each other, software testing, and problem solving), their original purpose was to be used for creating sandbox environments, an optimal way to test operating systems, without making permanent changes to the system and or affecting it, typically created via system ram, or harddrives via a program that creates the sandbox or in linux case it can simply be on a usb stick, until it is permanently installed, as whilst it remains uninstalled, it is also a virtual drive, system ram could also be used as temporary fast harddrive, to optimize games for example, due to using system memory to create a virtual drive of which you can place the installed game on to it, as system ram was much faster then a mechanical internal hdd as such for games this could greatly reduce loading times, but this was largely before SSDs became popular, but likewise the virtual drives created in this manner would only be temporary (for as long as the current session is active) due to how system ram works. essentially virtual drives are basically temporary harddrives that does not store permanent data, as the data is erased / or a new virtual drive is created whenever a new Session is Created (which would be a system restart) a good example of this, is putting Linux on a usb stick, you can mess around with it, install programs and the like, but if you don't install linux itself in that session, whenever you restart the computer and load back into it, it will be a completely new fresh start, any changes you made / programs installed prior to that is lost, unless said programs was installed on to a physical partition.

 

as such having the impression that m02 might potentially use virtual drives via noticing many posts of it supposedly using Virtual Drives, and with the knowledge of virtual drives in their technical form and purpose, i did assume that with m02 if it did indeed use virtual drives as the information presented would imply, then that would also imply that the virtual drives would only be created for as long as the program is launched, as said virtual drives are typically created via a program to create a sandbox, once that program closes or a new session is created, the data on the virtual drive is erased or simply a new virtual drive is created assuming it is system ram based.

 

but thinking about it now, m02 would very likely not be using actual virtual drives (not in the traditional sense at least), more likely it would actually be using a virtual file system, this would allow it to store data to permanent files, and likewise only make changes for as long as its open due to using a Virtual File System, where as if it used virtual drives in the traditional sense, the data (the installed mods themselves) would be lost every time a new session is created.

 

but with that said, i have very little knowledge on both Vortex and M02 as i have never used them, ever intend on using them or really researched them in great depth, as i very much live by the notion "if it aint broke dont fix it", been using NMM for a very long time now, ever since 2012 (before that i would do everything manually), and have never had any major problems with it (as such for me, it aint broke, thus their is no reason for me to upgrade to vortex or M02 or any other mod manager), it has been used to install and uninstall a plethora of mods throughout the years, both small and very large sized mods, without issues, as for regarding this topic, cbbe has been installed and unsintalled many many times through nmm, without a single problem every time, which is why it was confusing to see so many problems with installing cbbe via Vortex and M02, especially if Vortex for example supposedly uses the exact same method as NMM, now that is why i assumed originally that Vortex might of used Virtual Drives, because that makes a lot more sense in the potential issues that said reports of CBBE having issues with Vortex, based on knowing how Virtual Drives work in the technical sense.

 

so for me, regarding and likewise potentionally offering solutions with cbbe and vortex was strictly based on the assumption it was using virtual drives via reading many posts assuming it did, as such it was simply lack of experience on my part (as i never used them) and likewise lack of knowledge of both programs because of that, entirely basing my assumptions around what i have read, which would be them supposedly using virtual drives.

Edited November 17, 2022 by G4M3W1NN3R

[StormWolf01]

Indeed, a technical aspect of a VD goes a lot further than the functions of the mod managers. Especially since files are installed, that are meant to be semi-permanent/permanent.

I've played around with some VD environments. Particularly for IT testing to see how some apps would play with the network while sandboxed. Or whether employees/students could hide apps from the network thru VDs/VMs.

But yeah. At least with Vortex (which I myself only used very briefly, like... 3 years ago) it uses a substitute file system from what comments here on the forums suggests. And since 1ae hasn't offered a correction on that yet, I'm still gonna go with that train of thought.

Which in the case of some mods, means that the user has to install those files into the main game folders, themselves.

 

Which, in some cases, also means that users need to check their system settings, particularly in those folders. I myself have several folders in the game files that mysteriously set themselves as "Read Only". Which means for my changes to take effect, that I have to change the system properties for those folders when I want to make alterations to the contents. To remove those restrictions to the folders.

(This is probly due to me having my SDD mounted thru an optical drive bay, but it's a possibility that could affect other users too.)