Quote:
Originally Posted by aanker
Wow - can't have that........... did you start up SH4 in Career mode before installing RFB to check everything out in the Stock install first?
Then if SH4 ran fine before installing RFB it's either a Steam issue, SH4 location issue, JSGME issue, or RFB.
I don't know about how Steam interacts with mods but suspect everyone using Steam versions of SH4 would have said something if it was a problem, or needed special care.
Is SH4 installed to a folder off your C:\ or D:\ drive that you created - like I did called (for example):
C:\Subgames\Silent Hunter Wolves of the Pacific\sh4.exe - and other files & folders
- or to C:\username\Program Files\Silent Hunter Wolves of the Pacific\ ? <-- not recommended.
Did you configure the SH4 shortcut to start with sh4.exe - not gu.exe? gu.exe checks for needed updates before calling/permitting the sh4.exe file to start SH4.
After confirming SH4 started in Career mode, with an unmodded Vanilla Stock SH4 install using a sh4.exe shortcut, and then installing the JSGME, trying to start in Career mode again successfully, did you take a 'snapshot' of your files using that JSGME feature before installing RFB from the:
..... \Silent Hunter Wolves of the Pacific\MODS\ folder using the jsgme.exe in the ..... \Silent Hunter Wolves of the Pacific\ folder?
I can't think of anything else - possible bad RFB and/or RFB April Patch files?
Hopefully the issue is one of the others listed above - before installing RFB from the JSGME.
I'll check back - maybe someone will chime in about Steam versions too.
-
|
Well I am doing another clean install of it to test to see if it works. As for its location it is in program files but not on the main drive that windows operates from. Thou thats the folder steam decided to put all my games in. Thou really do not see the problem of folder placement when mods for sh5 work fine with it being in there and mods for skyrim working well as well.
P.S. Well the vanilla version works just fine. Going to try the mod again.
P.S.S. Well seems to fix the problem by switching the shortcut on main desktop with one manually made from within the folder itself. NVM. It work once then went right back to the same problem.