At some point my Modmgr decided to go to lunch. Have searched forums for hours and cant find anything similiar to this problem. I am realitively new to rF2, but ran rF1 since it came out. With rF1 I had a lot of lite installs for different mods to avoid conflicts and, also had my all my tarmac tracks and dirt tracks in two folders, just redirecting the track Dir paths. Was hoping to setup rF2 in a similiar fashion using the Modmgr when it decided to abort the project. Can not pinpoint anything that may have triggered it to stop launching, in fact I had not got around to even using it for anything, I was just aware it was there. I have installed the runtimes having read this rectified some other issues, yet still unaware of their actual purpose, no result. Complete new lite install, not over the top of exsisting and still no result. So my questions are 1: Why won't Modmgr start? and 2: If at some point I get it working, can I use it to setup rF2 in a similiar way to how I had rF1 setup?? Windows 7. Thanks Dave.
OK I'll try a different question. Does the old Mod manager still work with build 1008? I've done a complete new install of lite and dev into the default paths and still no Modmgr, just says it has stopped working and windows is looking for a solution as if the path is wrong. I have all my lite installs on a different drive and thought that was the problem, so tried the above. I would even feel a lot better if someone who doesn't have a clue would answer with 'No idea mate". so if like me you have just been reading the forums for ages and not posted anything, heres your chance. Dave.
Works flawless here as always. About multiple installs: I think rF2 is not intended to work like that in this regard. However, some people here have more than one install (when I remember correctly), so should work.
I have multiple installs and they work flawless. I use old mod manager in all of them. Enviado desde mi GT-I9505 mediante Tapatalk
Thanks guys, That can only mean I am missing something in windows that enables modmgr to open....? I don't recall anything else having issues. Does anybody know or have any ideas what modmgr requires to open? I am at a loss. Have tried opening as an administrator, checked through event viewer after trying to start it and get the usual cryptic error report windows dishes out. Note, it is the only error reported for months. Log Name: Application Source: Application Error Date: 23-Oct-15 6:10:32 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Stimulator Description: Faulting application name: ModMgr.exe, version: 0.9.3.20, time stamp: 0x55e5ee8a Faulting module name: ModMgr.exe, version: 0.9.3.20, time stamp: 0x55e5ee8a Exception code: 0x40000015 Fault offset: 0x0017ca38 Faulting process id: 0x110c Faulting application start time: 0x01d10d05b3a13a27 Faulting application path: B:\RF2 MODS\GT3\Bin32\ModMgr.exe Faulting module path: B:\RF2 MODS\GT3\Bin32\ModMgr.exe Report Id: f215b89e-78f8-11e5-b9c7-f46d046445e1 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-10-22T20:10:32.000000000Z" /> <EventRecordID>10206</EventRecordID> <Channel>Application</Channel> <Computer>Stimulator</Computer> <Security /> </System> <EventData> <Data>ModMgr.exe</Data> <Data>0.9.3.20</Data> <Data>55e5ee8a</Data> <Data>ModMgr.exe</Data> <Data>0.9.3.20</Data> <Data>55e5ee8a</Data> <Data>40000015</Data> <Data>0017ca38</Data> <Data>110c</Data> <Data>01d10d05b3a13a27</Data> <Data>B:\RF2 MODS\GT3\Bin32\ModMgr.exe</Data> <Data>B:\RF2 MODS\GT3\Bin32\ModMgr.exe</Data> <Data>f215b89e-78f8-11e5-b9c7-f46d046445e1</Data> </EventData> </Event> All that does for me is complicate things. But your help has narrowed the search fellas. Thanks again, Dave.
Sometimes the registry entries for ModMgr get messed up and then the tool fails to launch. Run a cmd prompt as admin and then run this command: Code: REG DELETE "HKCU\SOFTWARE\Image Space Incorporated\rFactor2 Mod Manager" /F