- Site Map >
- Community >
- Sims Discussion >
- Sims 2 >
- Sims 2 Help >
- Other - [SOLVED] BodyShop Won't Open, Any Alternatives?
- Site Map >
- Community >
- Sims Discussion >
- Sims 2 >
- Sims 2 Help >
- Other - [SOLVED] BodyShop Won't Open, Any Alternatives?
Replies: 24 (Who?), Viewed: 921 times.
#1
11th Jun 2022 at 10:37 AM
Last edited by ScrawnyTreeDemon : 16th Jul 2022 at 5:40 PM.
Posts: 15
This user has the following games installed:
Sims 2, University, Nightlife, Open for Business, Pets, Seasons, Bon Voyage, Free Time, Apartment Life
[SOLVED] BodyShop Won't Open, Any Alternatives?
This is my first time posting here, so bear with me.My neighbourhood is corrupted, so I've elected to go through the process of extracting all my Sims' appearances, in the hopes of cloning them. The issue is, is that no matter what I do, BodyShop will not open. Again, and again, I have used the correct version, taken out some of my CC, all of my CC, ran it through compatibility mode again, and again, and again, until my brain turned to sludge. It has been an exhausting endeavour, when all I want to do is to remake the hood I love.
Are there any ways to clean the extracted appearances otherwise? Though unlikely, are there any alternatives to BodyShop? Would such a thing even be possible? I ask this because it is endlessly frustrating that a program which shipped with the game can be so unreliable.
Cheers.
Advertisement
#2
11th Jun 2022 at 12:57 PM
Posts: 16,774
Thanks: 1745 in 10 Posts
If either the game or BodyShop doesn't open, the first thing to do is to delete the cache files, which you don't mention doing. Have you done this?
Most of the time, if you open the sims 2 folder, you will find the groups.cache and accessories.cache sitting there outside of all the subfolders. The game generates them as a handy reference full of frequently-accessed information to make things go a little faster, like a post-it note stuck to the side of your computer screen with info you'll need today scribbled on it. But, like that post-it note, over time (which varies a great deal from system to system), the cache files will get overwritten to the point of illegibility and have to be replaced; and Bodyshop and the game, although they reference the same cache files, don't seem to be able to use them the same way, and the program gets bewildered and can't even open if it can't cope with the cache files. So you delete them and the programs make new ones next time they save.
Usually I find it's enough to delete the groups.cache if the game won't open, but when switching between Bodyshop and the game i delete both simply because it's sometimes necessary and it takes so long to even be sure Bodyshop is thinking about opening that it's less tedious to do them both at once.
Bodyshop will also generate other new files in the same place, which in my experience will prevent my game from opening: cigen.package and, oh, I forget the other. Since the cache files are the only things in my game outside of subfolders, I just open The Sims 2 file and delete the files sitting in there loose that generated the day I opened Bodyshop.
I have myself played corrupted hoods for years without any major difficulties, because each case of corruption is unique and the degree of severity varies a great deal. The occasional strange want can be played around. It's only when cats behave and distort their forms trying to be humaniform, sims start disappearing, random crashing becomes unbearable, or the hood itself disappears, that I personally consider a neighborhood unplayable. So you may as well play a bit while you're sorting it out and give yourself some relief, maybe?
Anyway, good luck and happy simming.
Ugly is in the heart of the beholder.
(My simblr isSim Media Res . Widespot,Widespot RFD: The Subhood, and Land Grant University are all available here. In case you care.)
Most of the time, if you open the sims 2 folder, you will find the groups.cache and accessories.cache sitting there outside of all the subfolders. The game generates them as a handy reference full of frequently-accessed information to make things go a little faster, like a post-it note stuck to the side of your computer screen with info you'll need today scribbled on it. But, like that post-it note, over time (which varies a great deal from system to system), the cache files will get overwritten to the point of illegibility and have to be replaced; and Bodyshop and the game, although they reference the same cache files, don't seem to be able to use them the same way, and the program gets bewildered and can't even open if it can't cope with the cache files. So you delete them and the programs make new ones next time they save.
Usually I find it's enough to delete the groups.cache if the game won't open, but when switching between Bodyshop and the game i delete both simply because it's sometimes necessary and it takes so long to even be sure Bodyshop is thinking about opening that it's less tedious to do them both at once.
Bodyshop will also generate other new files in the same place, which in my experience will prevent my game from opening: cigen.package and, oh, I forget the other. Since the cache files are the only things in my game outside of subfolders, I just open The Sims 2 file and delete the files sitting in there loose that generated the day I opened Bodyshop.
I have myself played corrupted hoods for years without any major difficulties, because each case of corruption is unique and the degree of severity varies a great deal. The occasional strange want can be played around. It's only when cats behave and distort their forms trying to be humaniform, sims start disappearing, random crashing becomes unbearable, or the hood itself disappears, that I personally consider a neighborhood unplayable. So you may as well play a bit while you're sorting it out and give yourself some relief, maybe?
Anyway, good luck and happy simming.
Ugly is in the heart of the beholder.
(My simblr isSim Media Res . Widespot,Widespot RFD: The Subhood, and Land Grant University are all available here. In case you care.)
#3
11th Jun 2022 at 1:11 PM
Posts: 8,912
Thanks: 3128 in 87 Posts
Here: https://modthesims.info/showthread.php?t=667347
Windows 10 and the Ultimate Collection
http://modthesims.info/showthread.php?t=568275
http://modthesims.info/showthread.php?t=614833
Windows 10 and the Ultimate Collection
http://modthesims.info/showthread.php?t=568275
http://modthesims.info/showthread.php?t=614833
#4
11th Jun 2022 at 2:10 PM
Posts: 12,994
Thanks: 3 in 1 Posts
"Cigen.package" - has the Bodyshop thumbnails (can be useful to keep if you find Bodyshop loads the thumbnails slowly, especially if you have lots of CAS content, and it isn't always necessary to delete. You can delete individual thumbnails from it in SimPE if you just want to refresh a few, although they can be difficult to find).
"Contentregistry" - I usually delete this one if I've created something.
---
Are you using the proper version of Bodyshop? Make sure it's the one in the highest EP folder (or in the M&G folder).
If you're running with Windows 10, compatibility mode might not work (especially if you're using the 4GB patch). If your game needed to get to know your graphic card and all that, Bodyshop likely needs to go through the same process - GraphicRules and 4GB patch at the minimum (in the "TSData\Res\CSConfig" and "CSBin" folder, highest EP or M&G).
"Contentregistry" - I usually delete this one if I've created something.
---
Are you using the proper version of Bodyshop? Make sure it's the one in the highest EP folder (or in the M&G folder).
If you're running with Windows 10, compatibility mode might not work (especially if you're using the 4GB patch). If your game needed to get to know your graphic card and all that, Bodyshop likely needs to go through the same process - GraphicRules and 4GB patch at the minimum (in the "TSData\Res\CSConfig" and "CSBin" folder, highest EP or M&G).
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
#5
11th Jun 2022 at 8:00 PM
Posts: 15
Ahh, forgot to specify! But yeah, I clean my cache regularly-- Did so several times in between opening attempts, too. It helps in dealing game crashes(though I suspect those are due to bad custom content, which I'll have to look through sometime), but it hasn't done anything to help BodyShop. In turn, while I know I'll probably manage for a good while longer, at the same time I do want to deal with it now. I've been putting it off for awhile now, as-is.
Yeah, I use the M&G version; it's what I mean by the 'correct' version. Thank you for the pointers on compatibility! Makes sense, with that accounted. Another issue has cropped up, though, and that is that GRM is seemingly convinced BodyShop is in the same folder as the game when I select specifically for it in the dropdown-- Which it is not(it's in CSBin, as expected), and when I tell it otherwise, it can't detect it, even when I go in there and browse myself. It won't show up.
As for Justpetro's addition, thank you! It's yet to have an effect yet, but fingers crossed if I can get GRM to work, it'll help
Thank you all for you responses. Here's hoping we can get to the bottom of this.
---
UPDATE!
It ran in the background for a few seconds, instead of not starting at all, which is certainly an improvement. If anything comes of this, I will let you all know.
Yeah, I use the M&G version; it's what I mean by the 'correct' version. Thank you for the pointers on compatibility! Makes sense, with that accounted. Another issue has cropped up, though, and that is that GRM is seemingly convinced BodyShop is in the same folder as the game when I select specifically for it in the dropdown-- Which it is not(it's in CSBin, as expected), and when I tell it otherwise, it can't detect it, even when I go in there and browse myself. It won't show up.
As for Justpetro's addition, thank you! It's yet to have an effect yet, but fingers crossed if I can get GRM to work, it'll help
Thank you all for you responses. Here's hoping we can get to the bottom of this.
---
UPDATE!
It ran in the background for a few seconds, instead of not starting at all, which is certainly an improvement. If anything comes of this, I will let you all know.
#6
11th Jun 2022 at 8:15 PM
Posts: 12,994
Thanks: 3 in 1 Posts
If you have a lot of CC, it often takes a while for Bodyshop to start up. Run Task manager and find Bodyshop in the list, to see if it's actually running.
Alternatively, temporarily move out your CC, clean the cache, and then run Bodyshop - it will run a lot faster and won't crash on startup in case you've got some bad CC lurking around that's making it do so.
Try copy/replacing the fixed GraphicRules file from the Config folder to the CSConfig folder (assuming the one in your Config folder is set up properly). That solves the "GRM can't find Bodyshop" issue.
Alternatively, temporarily move out your CC, clean the cache, and then run Bodyshop - it will run a lot faster and won't crash on startup in case you've got some bad CC lurking around that's making it do so.
Try copy/replacing the fixed GraphicRules file from the Config folder to the CSConfig folder (assuming the one in your Config folder is set up properly). That solves the "GRM can't find Bodyshop" issue.
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
#7
12th Jun 2022 at 7:03 AM
Posts: 15
Quote: Originally posted by simmer22
If you have a lot of CC, it often takes a while for Bodyshop to start up. Run Task manager and find Bodyshop in the list, to see if it's actually running. Alternatively, temporarily move out your CC, clean the cache, and then run Bodyshop - it will run a lot faster and won't crash on startup in case you've got some bad CC lurking around that's making it do so. Try copy/replacing the fixed GraphicRules file from the Config folder to the CSConfig folder (assuming the one in your Config folder is set up properly). That solves the "GRM can't find Bodyshop" issue. |
I've looked through, and while sometimes it starts up, it's never for more than a few seconds in the background. There's no crashing, it just never gets past that first stage. Did move the CC out and cleared that scrap of cache while I tried the next step, though.
Did as you suggested, though I think I realise there wasn't any problem in that regard-- It's just that you're not meant to delve into subfolders specifically. The same "issue" would crop up if I attempted it with the main game in TSBin, and that works just fine as is(I hope I'm making sense?). Applied the 4GB patch manually, too.
All this to say that... I still can't get it to run. This is driving me to my wits' end. Again, thank you for your help-- Let's see if we can figure this out.
I know this is a more speculative question, but has anybody tried, or is it even possible to have a community-made alternative to BodyShop, considering we don't have the source code? Hell, for my purposes, a full mirror wouldn't be necessary, just something that can clean the exported appearances.
Cheers.
#8
12th Jun 2022 at 2:19 PM
Posts: 12,994
Thanks: 3 in 1 Posts
Have you run your game after trying Bodyshop? If not, can you post your Config-Log from the Logs folder in the Documents location? It could give some clues as to why Bodyshop isn't running (it's enough to post Application info down to where Global Properties starts. Make sure the Application info says "Name: The Sims 2 Body Shop" - if it doesn't, try running Bodyshop again - doesn't matter if it doesn't want to run, it's just to get the file to pick up the info from Bodyshop and not from the game)
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
#9
13th Jun 2022 at 6:54 PM
Posts: 15
Quote: Originally posted by simmer22
Have you run your game after trying Bodyshop? If not, can you post your Config-Log from the Logs folder in the Documents location? It could give some clues as to why Bodyshop isn't running (it's enough to post Application info down to where Global Properties starts. Make sure the Application info says "Name: The Sims 2 Body Shop" - if it doesn't, try running Bodyshop again - doesn't matter if it doesn't want to run, it's just to get the file to pick up the info from Bodyshop and not from the game) |
Had to do some finicking around with my GraphicsRules(DirectX error because I logged my graphics card, lmao), ended up applying the fix for that, and that actually ended up getting it to a point where it could start. It still ended up crashing, but hey! Tried again first without the Build items(of which the bad CC is probably a part), and then all the CC, but the crash still happened.
Here's the section of that log, BodyShop as you specified:
Code:
Global properties ----------------- uintProp propertyRevision 5 boolProp animationLOD false uintProp antialiasingQuality 0 boolProp autoCentering true boolProp bumpMapping false boolProp constrainFloorElevation true uintProp cutawayMemorySize 3 boolProp cutawayOutside true boolProp deviceVsynch true boolProp displayLookAtBoxes false boolProp displayPaths false uintProp dynamicRenderStrategy 0 boolProp edgeScrolling false uintProp effectPriorityLevel 3 stringProp lastLoadedNeighborhood boolProp freeWill true floatProp geomBoneInfluenceThreshold 0.01 boolProp geomCheckGeomDataIntegrity false uintProp geomGenerateTangentSpaceNormalLines 0 boolProp geomGenerateTangentSpaceSxT false floatProp geomGeneratedTangentSpaceNormalLineLength 0.1 uintProp geomMaxBoneInfluencesPerVertex 4 sintProp geomMaxMorphTargetDeltasPerVertex 4 floatProp geomMorphTargetDeltaThreshold 0.001 floatProp geomPerBoneBoundBlendWeightThreshold 0.9 boolProp guob true boolProp interrupt false boolProp lightOpenGLStyle false uintProp lightingQuality 3 boolProp livePIP true stringProp lotWindowFillColor (0,0,0,1) uintProp maxParticlesTarget 10000 uintProp maxTerrainGrade 5 boolProp morph true stringProp neighborhoodWindowFillColor (0.5,0.5,0.5,1) boolProp noStupidIFFUnlocking false boolProp optimizeMeshes true floatProp particleDamping 0 floatProp particleDensity 1 uintProp particleLODOffset 0 floatProp particleScale 1 floatProp particleSizeThreshold 1 boolProp quickTips true boolProp reduceBoneWeights false boolProp renderOpaqueUI false boolProp reflectionWithExtraViewer false boolProp nhoodWaterReflection false boolProp renderInsideObjectOnlyOnSelectedSimLevel false boolProp renderSelectedSimLevel false boolProp simInBackground false boolProp sleepInBackground true boolProp simShadows true boolProp snapObjectsToGrid true uintProp soundDetail 2 boolProp specHighlights true boolProp unevenTilesFloorable true boolProp useEffects true boolProp useLODs false uintProp snapshotPictureQuality 2 uintProp snapshotPictureSize 2 uintProp videoCaptureMaxRecordingSeconds 30 uintProp videoCaptureQuality 1 uintProp videoCaptureSize 1 boolProp videoCaptureAudioOn true boolProp CameraDriftCamEnabled true boolProp CameraSpecialEventEnabled true boolProp SoundMasterGroupVoxEnabled true boolProp SoundMasterGroupFXEnabled true boolProp SoundMasterGroupMusicEnabled true boolProp SoundMasterGroupAmbienceEnabled true uintProp FXVolume 100 uintProp VOXVolume 100 uintProp AmbienceVolume 100 uintProp MusicVolume 50 uintProp AudioPerformance 1 boolProp perfAddLights true boolProp perfRenderParts true boolProp perfLightCaching true boolProp perfEnableSkinning true boolProp perfEnableMorphing true uintProp lodOverride 0 boolProp autoLogin false boolProp floorCollisions true boolProp wallCollisions true Device 0 -------- Options ------- uintProp MaterialDetail 1 #default: 1 uintProp ObjectDetail 2 #default: 2 uintProp ObjectHiding 1 #default: 1 uintProp SnowOnGround 1 #default: 1 uintProp Shadows 1 #default: 1 uintProp OpaqueUI 0 #default: 0 uintProp Reflection 0 #default: 0 uintProp Ceiling 0 #default: 0 uintProp EffectsQuality 1 #default: 1 uintProp LightingQuality 1 #default: 1 uintProp SoundQuality 1 #default: 1 uintProp DirtyRect 2 #default: 2 uintProp FullscreenFadeEffect 1 #default: 1 uintProp Turbo 2 #default: 2 uintProp SimulatorControls 1 #default: 1 uintProp LightingOptimizations 3 #default: 3 uintProp AnimationSamplingLevel 1 #default: 1 uintProp LivePIP 0 #default: 0 uintProp SpecialEventCamera 1 #default: 1 uintProp ScreenModeResolution 3 #default: 3 uintProp SubjectTracking 1 #default: 1 uintProp EnableLotImpostersInLot 0 #default: 0 uintProp EnableNeighborhoodOccupantsInLot 0 #default: 0 uintProp LotSkirtSizeIncrease 0 #default: 0 Option properties ----------------- boolProp bumpMapping false uintProp imageDataSizeReductionOnLoad 2 boolProp reduceBoneWeights true boolProp useLODs true uintProp lodOverride 35 uintProp renderInsideVisibleObjects 1 boolProp showSnowOnGround true boolProp simShadows false boolProp objectShadows false boolProp guob false boolProp heightMapShadows false boolProp renderOpaqueUI false boolProp reflectionWithExtraViewer false boolProp nhoodWaterReflection false boolProp includeCeilings false boolProp useEffects true boolProp enableOceanReflection false uintProp maxParticlesTarget 2000 uintProp particleLODOffset 0 uintProp effectPriorityLevel 1 floatProp particleDensity 1 floatProp particleScale 1 boolProp lightingEnabled true boolProp portalLighting false boolProp floorAndWallNormalMapping false boolProp specHighlights false uintProp AudioPerformance 0 uintProp dynamicRenderStrategy 2 boolProp enableSnapshot true boolProp useTurboRect true uintProp maxNumOfVisitingSims 2 boolProp optimizedDiffusion true boolProp incrementalLighting true boolProp lerpLights true boolProp useDirtyTiles true boolProp animationFrameSampling true boolProp livePIP false boolProp livePIPDefault false boolProp chooseCameraSpecialEventEnabled true uintProp maxResWidth 1600 uintProp maxResHeight 1200 uintProp defaultResWidth 1024 uintProp defaultResHeight 768 floatProp centerTrackingDeadZoneMagnitude 70 boolProp enableLotImpostersInLot false boolProp enableNeighborhoodOccupantsInLot false uintProp lotSkirtSizeIncrease 5 uintProp optionMaterialDetail 1 uintProp optionObjectDetail 2 uintProp optionObjectHiding 1 uintProp optionSnowOnGround 1 uintProp optionShadows 1 uintProp optionOpaqueUI 0 uintProp optionReflection 0 uintProp optionCeiling 0 uintProp optionEffectsQuality 1 uintProp optionLightingQuality 1 uintProp optionSoundQuality 1 uintProp optionDirtyRect 2 uintProp optionFullscreenFadeEffect 1 uintProp optionTurbo 2 uintProp optionSimulatorControls 1 uintProp optionLightingOptimizations 3 uintProp optionAnimationSamplingLevel 1 uintProp optionLivePIP 0 uintProp optionSpecialEventCamera 1 uintProp optionScreenModeResolution 3 uintProp optionSubjectTracking 1 uintProp optionEnableLotImpostersInLot 0 uintProp optionEnableNeighborhoodOccupantsInLot 0 uintProp optionLotSkirtSizeIncrease 0 sintProp activeDeviceNum 0 Device properties ----------------- boolProp useRenderTextures false uintProp antialiasingSupport 1 boolProp dontMergeNHFlora true boolProp enableDriverMemoryManager false boolProp vs2LoopsFunctional false boolProp presentWorkaround false boolProp enumerateMultisampleLevels true boolProp disableVSyncSupport true boolProp disableTexMemEstimateAdjustment true uintProp deviceLocalVideoMemorySizeDefault 1744830464 boolProp activeDeviceUseSoftwareRasterizer false uintProp configParserErrorCode 0 uintProp hwMajorPSVersion 3
Again, thank you so much! We're finally getting somewhere!
#10
13th Jun 2022 at 7:05 PM
Last edited by simmer22 : 13th Jun 2022 at 7:15 PM.
Posts: 12,994
Thanks: 3 in 1 Posts
I meant everything above "Global properties" (Application info, Machine Info, graphic device info, etc.)
The info below "Global Properties" is just various properties/cheats enabled for your game via the GraphicRules or UserStartup files.
Are you editing the GraphicRules file in Config or CSConfig?
The one in CSConfig is the one that controls the info for Bodyshop.
The info below "Global Properties" is just various properties/cheats enabled for your game via the GraphicRules or UserStartup files.
Are you editing the GraphicRules file in Config or CSConfig?
The one in CSConfig is the one that controls the info for Bodyshop.
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
#11
13th Jun 2022 at 7:59 PM
Posts: 15
Quote: Originally posted by simmer22
I meant everything above "Global properties" (Application info, Machine Info, graphic device info, etc.) The info below "Global Properties" is just various properties/cheats enabled for your game via the GraphicRules or UserStartup files. Are you editing the GraphicRules file in Config or CSConfig? The one in CSConfig is the one that controls the info for Bodyshop. |
Ahh, okay! Here that is:
Code:
=== Application info === Name: The Sims 2 Body Shop Version: 1.17.0.66 Build: ReleaseSRT === Machine info === OS version: Windows NT 6.2 CPU: 2097.199951Mhz, Name:GenuineIntel, FPU:1, MMX:1 Memory: 4096MB Free memory: 3288MB User: *NAME* Computer: CLARET-560 === Sound device info === Name: Unknown Driver: Unknown === Graphics Rules Maker Configuration === Force texture memory: 4017 Mb Disable Texture Memory Estimate Adjustment: No Enable Driver Memory Manager: Yes Disable Sims Shadows: No Radeon HD7000 fix: No Intel High Quality: No Intel V-Sync: No Default Resolution: 2736x1824 Maximum Resolution: 2736x1824 === Graphics device info === Number: 0 Name (driver): Intel(R) Iris(R) Plus Graphics Name (database): Intel(R) Iris(R) Plus Graphics Vendor: Intel Chipset: Vendor: 8086, Device: 8a5a, Board: 00371414, Chipset: 0007 Driver: igdumdim32.dll, Version: 27.20.100.9621, GUID: D7B78E66-C91A-11CF-3152-5320BCC2D635 Driver version: 9621 Monitor: \\.\DISPLAY1 Monitor aspect: 1.502890, <<UNRECOGNIZED>> Screen mode: 2736x1824x32BPP,59Hz Texture memory: 4017MB HW T&L: Fixed function:1 Programmable:3.0 Pixel program: 3.0 Texture stages: 8 AppControlledAA: 1
CSConfig GR has the same data as Config GR, so yes.
Ran into a glitch that, thankfully, wasn't graphical as I feared but had to do with an innocuous cache clearing setting in my launcher - But I bring it up because it's added to the stress. Trying to hold out hope, but yeah... What alot of toil for one application.
Can't use GRM to edit my GR file anymore, all because I enabled recognition for my card in the 'Device Info' section. Anytime I save the file, it makes it so that the game runs into a DirectX9 error-- What a fucking pain. I don't know why. It was perfectly fine before. Tried uninstalling and reinstalling, but the recognition remained. It makes enabling all the options I need that much more difficult, and I can only imagine it's adding to it.
Seriously, I'm sorry if this grating you. Your patience is astounding. I feel like I'm running to my wits' end, here, having to run around in circles over, and over again, only for more shit to show up. I'm exhausted.
#12
13th Jun 2022 at 9:07 PM
Posts: 12,994
Thanks: 3 in 1 Posts
Do you have dual graphics, or just the intel chip?
Don't pick "do not force" for texture memory, but make sure it says a number (auto-detects your settings) - apparently the "do not force" can cause the Dirextx9 bug. For the game, windowed mode can help (Bodyshop is already windowed, so it shouldn't have that problem).
You can also try to set the max resolution for Bodyshop to 1920x1080.
The "Disable texture memory estimate adjustment" box could be helpful to tick, too (it ihelps for Nvidia cards, used to be a bug in the GRM that caused pink-soup/crashing, even in Bodyshop - not sure if it helps for Intel chips, though)
Don't pick "do not force" for texture memory, but make sure it says a number (auto-detects your settings) - apparently the "do not force" can cause the Dirextx9 bug. For the game, windowed mode can help (Bodyshop is already windowed, so it shouldn't have that problem).
You can also try to set the max resolution for Bodyshop to 1920x1080.
The "Disable texture memory estimate adjustment" box could be helpful to tick, too (it ihelps for Nvidia cards, used to be a bug in the GRM that caused pink-soup/crashing, even in Bodyshop - not sure if it helps for Intel chips, though)
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
#13
13th Jun 2022 at 9:41 PM
Posts: 15
Quote: Originally posted by simmer22
Do you have dual graphics, or just the intel chip? Don't pick "do not force" for texture memory, but make sure it says a number (auto-detects your settings) - apparently the "do not force" can cause the Dirextx9 bug. For the game, windowed mode can help (Bodyshop is already windowed, so it shouldn't have that problem). You can also try to set the max resolution for Bodyshop to 1920x1080. The "Disable texture memory estimate adjustment" box could be helpful to tick, too (it ihelps for Nvidia cards, used to be a bug in the GRM that caused pink-soup/crashing, even in Bodyshop - not sure if it helps for Intel chips, though) |
Just the one!
That fixed the game loadup, thank you! I already play my game in windowed, so that certainly helps.
BodyShop still opens, loads quickly, the bar gets almost a third of the way through, then crashes(even with cache cleared CC taken out). But! At least we have stable ground to go off of.
#14
13th Jun 2022 at 10:27 PM
Posts: 12,994
Thanks: 3 in 1 Posts
Does the computer/laptop only have 4GB RAM? That could explain some of the issues, especially if you're using Windows 10 (possibly also 11). The 4GB patch might not work very well unless you have 6GB or more.
Do you have any CC/mods in the install location, like recategorizers and such? If so, try without.
Do you have any CC/mods in the install location, like recategorizers and such? If so, try without.
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
#15
13th Jun 2022 at 11:05 PM
Posts: 15
Quote: Originally posted by simmer22
Does the computer/laptop only have 4GB RAM? That could explain some of the issues, especially if you're using Windows 10 (possibly also 11). The 4GB patch might not work very well unless you have 6GB or more. Do you have any CC/mods in the install location, like recategorizers and such? If so, try without. |
8 gigs, actually! 7.6 of them are usable, but it's more than enough.
I'll go ahead and do that... tomorrow. It's late, and I've had a long day, haha. I'm not sure it'll work, considering taking out the content did nothing but speed the bar filling, resulting in a crash all the same, but I get the sense we're running out of options.
Again, if there's a way to clean these extracted appearances via another method, I'll take it. Doesn't have to be pretty, just has to work. If for whatever reason someone out there decides to pick it up, I'll wait as long as I need.
Thank you again. It really means alot.
#16
24th Jun 2022 at 6:11 PM
Posts: 15
Returning several days later to say that that wouldn't have helped. I made a new, completely empty hood to play around for a bit, and I experienced *none* of the crashes and various bugs present in my main hood. It's just plain corrupted.
This isn't a bump, I'm saying this now, albeit very late, as means of further documentation.
I hate to ask, would it even be *possible* to have a third-party program capable of cleaning out extracted Sim appearances? Not does it exist, not if anyone has plans to do such a thing, but is it *possible*? Because if not, then I'm shit outta luck.
I want to thank everyone who contributed for the time and effort. This whole endeavour has been a real stumper, and my head hurts just thinking about it. What a pain.
This isn't a bump, I'm saying this now, albeit very late, as means of further documentation.
I hate to ask, would it even be *possible* to have a third-party program capable of cleaning out extracted Sim appearances? Not does it exist, not if anyone has plans to do such a thing, but is it *possible*? Because if not, then I'm shit outta luck.
I want to thank everyone who contributed for the time and effort. This whole endeavour has been a real stumper, and my head hurts just thinking about it. What a pain.
#17
16th Jul 2022 at 5:40 PM
Last edited by ScrawnyTreeDemon : 16th Jul 2022 at 7:17 PM.
Reason: Edit
Posts: 15
Update!
I think I found the issue! For some reason, having the SavedSims folder is what crashes BodyShop. I don't know if it's because I created it, or the Sims in it are Jank™, but without it the program loads just fine. How weird.Regardless how exactly I'm going to clone, what matters is that the program even works at all. I know I'm sounding like a broken record, but thank you again everyone who helped. I'll mark the thread as solved, as the main issue has been fixed.
Lots of love <3 <3 <3
Edit: looks to have been a case of too many at once. On top of that, apparently it's best to rename those generated .package files, as the names SimPE puts out can crash BodyShop. With that in mind, I am cloning just fine now. Thank goodness :P
#18
16th Jul 2022 at 10:38 PM
Posts: 12,994
Thanks: 3 in 1 Posts
Bodyshop should be able to create the SavedSims folder when you make sims or CC with it. If you made the folder or had something in it that Bodyshop didn't like, it's not too weird Bodyshop crashed. Bodyshop can be iffy with such things.
---
Make sure to clone the sims in Bodyshop after you extract them with SimPE, then remove the original extracted sims before you open your game, only keeping the clones. Otherwise you can risk corruption.
If you want to package sims for later use, make sure you package clones. If you package extracted sims they won't pull CC, and the packaged sim is the extracted one, which can potentially cause corruption in your game (or someone else's if you upload them).
The naming of extracted sims is apparently a bit spesific. I had some issues last time I tried extracting sims (I don't do it all that often). Can't remember exactly what caused the issue, but it had to do with how I'd named the extracted files. I think I found it worked fine to use the name of the sim, but using numbers in the front or other characters wasn't too agreeable. Probably has to do with how the neighborhood characters are named.
---
Make sure to clone the sims in Bodyshop after you extract them with SimPE, then remove the original extracted sims before you open your game, only keeping the clones. Otherwise you can risk corruption.
If you want to package sims for later use, make sure you package clones. If you package extracted sims they won't pull CC, and the packaged sim is the extracted one, which can potentially cause corruption in your game (or someone else's if you upload them).
The naming of extracted sims is apparently a bit spesific. I had some issues last time I tried extracting sims (I don't do it all that often). Can't remember exactly what caused the issue, but it had to do with how I'd named the extracted files. I think I found it worked fine to use the name of the sim, but using numbers in the front or other characters wasn't too agreeable. Probably has to do with how the neighborhood characters are named.
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
#19
18th Jul 2022 at 10:56 PM
Posts: 15
Quote: Originally posted by simmer22
Bodyshop should be able to create the SavedSims folder when you make sims or CC with it. If you made the folder or had something in it that Bodyshop didn't like, it's not too weird Bodyshop crashed. Bodyshop can be iffy with such things. --- Make sure to clone the sims in Bodyshop after you extract them with SimPE, then remove the original extracted sims before you open your game, only keeping the clones. Otherwise you can risk corruption. If you want to package sims for later use, make sure you package clones. If you package extracted sims they won't pull CC, and the packaged sim is the extracted one, which can potentially cause corruption in your game (or someone else's if you upload them). The naming of extracted sims is apparently a bit spesific. I had some issues last time I tried extracting sims (I don't do it all that often). Can't remember exactly what caused the issue, but it had to do with how I'd named the extracted files. I think I found it worked fine to use the name of the sim, but using numbers in the front or other characters wasn't too agreeable. Probably has to do with how the neighborhood characters are named. |
Yes, yes, I know all this-- Went into all this with that methodology. It's why I was so keen on getting the program to run in the first place-- Wouldn't do any good recreating the hood only for stray character data to fuck it all over again. No intent on packaging characters, but oh yeah, for sure. I always make sure to read up thoroughly before I try something-- You have to with this game.
Thank you for clarification on that! Yeah, I've settled on labelling them with the Sims' names too-- Solves that issue, and makes it easier to navigate.
Glad to put this behind me, thank god.
Instructor
#20
26th Jul 2022 at 5:19 AM
Posts: 438
SimRetriever can possibly help extract your sims.
#21
26th Jul 2022 at 4:37 PM
Posts: 12,994
Thanks: 3 in 1 Posts
^ That program is meant to retrieve sims from a corrupted neighborhood. You still need Bodyshop to clone them after getting as far as extracting them with SimPE. https://modthesims.info/d/503733/simretriever.html (read Mootilda's description)
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
Instructor
#22
27th Jul 2022 at 2:22 PM
Posts: 438
Quote: Originally posted by simmer22
^ That program is meant to retrieve sims from a corrupted neighborhood. You still need Bodyshop to clone them after getting as far as extracting them with SimPE. https://modthesims.info/d/503733/simretriever.html (read Mootilda's description) |
Oh crap, you’re right. Would one be able to do it manually in SimPE, though? (It would be so tedious, however...)
#23
27th Jul 2022 at 2:53 PM
Posts: 12,994
Thanks: 3 in 1 Posts
If your sims aren't corrupted beyond SimPE's ability to read them, you don't need the extra program.
(Bodyshop is still needed, unfortunately - the sims you extract with SimPE are the actual character files, and these can potentially harm the game if you try using them as-is ingame, especially in a different neighborhood than they originally came from. When cloned in Bodyshop it extracts the face file and info about CAS items used, while any info about the actual sim is removed).
(Bodyshop is still needed, unfortunately - the sims you extract with SimPE are the actual character files, and these can potentially harm the game if you try using them as-is ingame, especially in a different neighborhood than they originally came from. When cloned in Bodyshop it extracts the face file and info about CAS items used, while any info about the actual sim is removed).
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
Instructor
#24
28th Jul 2022 at 4:38 AM
Posts: 438
Quote: Originally posted by simmer22
If your sims aren't corrupted beyond SimPE's ability to read them, you don't need the extra program. (Bodyshop is still needed, unfortunately - the sims you extract with SimPE are the actual character files, and these can potentially harm the game if you try using them as-is ingame, especially in a different neighborhood than they originally came from. When cloned in Bodyshop it extracts the face file and info about CAS items used, while any info about the actual sim is removed). |
Oh, I meant clearing out their memories and stuff manually through SimPE.
#25
28th Jul 2022 at 6:07 PM
Posts: 12,994
Thanks: 3 in 1 Posts
If you want a clone of the sims for use in CAS and Bodyshop, there's no need to clear out memories, etc. in SimPE. You just need to extract the sim with SimPE and then clone in bodyshop. The memory/family/etc. info won't follow the Bodyshop clone.
I don't know if it's possible (or in any way easy even if it is) to clear out all the info with SimPE and make a properly working face/sim file. Bodyshop is much easier since it makes a new file structure for the face file in a few easy steps anyone can follow.
I don't know if it's possible (or in any way easy even if it is) to clear out all the info with SimPE and make a properly working face/sim file. Bodyshop is much easier since it makes a new file structure for the face file in a few easy steps anyone can follow.
My site - TS2 baby stuff - ToU
My stories: Anna's diary - Memories are forever - Little Fire Burning
My stories: Anna's diary - Memories are forever - Little Fire Burning
Who Posted
|