Jump to content

Photo

Script Compilation Error

mod error script compilation

1 reply to this topic

#1
Themaxinator

Themaxinator

    Stranger

  • Members
  • Pip
  • 1 posts

Hey Guys, after installing some mods and merging them, i get the following script copilation errors:

 

Error [content0]game\player\playertutorialinput.ws(9): Unknown base class 'CPlayerInput'
Error [modimmersivecam]immersivecamconfig.ws(584): Unknown base class 'CPlayerInput'
 
Warning [modimmersivecam]game\player\states\aimthrow.ws(10): Adding state 'AimThrow' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\combat.ws(38): Adding state 'Combat' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\exploration.ws(14): Adding state 'Exploration' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [content0]game\player\states\extendedmovable.ws(6): Adding state 'ExtendedMovable' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [content0]game\player\states\skating.ws(19): Adding state 'Skating' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\swimming.ws(7): Adding state 'Swimming' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [content0]game\player\states\unconscious.ws(6): Adding state 'Unconscious' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [content0]game\player\states\vehicles\dismounthorse.ws(10): Adding state 'DismountHorse' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\vehicles\horseriding.ws(6): Adding state 'HorseRiding' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\vehicles\mountboat.ws( :cool:: Adding state 'MountBoat' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\vehicles\mountthevehicle.ws( :cool:: Adding state 'MountTheVehicle' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\vehicles\sailing.ws(10): Adding state 'Sailing' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modimmersivecam]game\player\states\vehicles\sailing.ws(376): Adding state 'SailingPassive' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
Warning [modbettertorches131]game\player\states\vehicles\usevehicle.ws(53): Adding state 'UseGenericVehicle' to class 'CR4Player' which is not a state machine. Did you forget the 'statemachine' keyword in class?
 
 
 
I have the following mods installed:
 
Over 9000 - Weight limit mod
Increased creature loot
Fast Travel from Anywhere
NoDirtyLenseEffect
FriendlyHUD
Super Turbo Lightning Mod
Immersive Cam
modMapQuestObejctives
Improved Signs Mod
High Quality Faces
More Shadows
Better Torches
Next Generation Level of Detail
HD Rework Project
Realistic Weather
Witcher ReEngaged
 
I also have the Unification Patch installed.
After Installing the mods I used the Script Merger to merge them.
 
If you have any idea how i could resolve these errors, or if you had similar problems in the past, please respond to this post.

Edited by Themaxinator, 19 July 2019 - 08:44 PM.


#2
Partoutatix

Partoutatix

    Faithful poster

  • Members
  • PipPipPipPip
  • 1,211 posts

Probably didn't place the unification patch or mod files in the right places, or you used vortex, or didn't use the script merger patch. I'd suggest you roll back your tw3 install to vanilla then proceed one mod at a time.

 

How to install most simple TW3 Mods for newbies/klutzes:

Spoiler:  
Show

First you gotta locate your The Witcher 3 game install location. Usually it's somewhere like "C:\GOG Games\The Witcher 3 Wild Hunt GOTY" for Good Old Games versions of the game or "C:\Program Files (x86)\Steam\steamapps\common\The Witcher 3" for Steam versions of the game.

Mandatory:
Script Merger
Download, run/install it, run what it installed to be sure it's working.
Script Merger Unofficial Patch:
Download, run/install it, run what it installed to be sure it's working.

Optional but highly recommended:
TW3 Mod Manager
Download, run/install it, run what it installed to be sure it's working. Installing it all to some place like C:\TW3Modding\ should work.
Mod Limit Fix
Download, run/install it, run what it installed to be sure it's working
Enable the Debug Console: https://www.nexusmod...cher3/mods/3375. Press the keys on your keyboard until you figure out which one activates the console.



After that you can install most mods by downloading them manually (VORTEX NOT RECOMMENDED WITH TW3 MODS, IT WILL EVENTUALLY CAUSE PROBLEMS). Extract their contents somewhere (rightclick on the downloaded mod file->extract) and then place their files&folders in the right places in your game install yourself OR let TW3 Mod Manager extract and place them correctly for you (Recommended). 

If you're not using TW3 Mod Manager you need to make sure all of your mod's \modxxx folders end up directly inside your <TW3 game install>\Mods folder (or <TW3 game install>\mods, wherever your other mods are). If there's no mods folder in your TW3 game install folder (TW3MM would've created one for you) you can create one by rightclicking on some empty space there -> "New" -> "Folder" and write Mods as its name. That means your \modxxx folders ends up as <TW3 game install>\Mods\modxxx. TW3MM would place it there automatically for you so you wouldn't have to.

If your mod has \dlcxxx folders they similarly need to be directly inside your <TW3 game install>\dlc folder (or <TW3 game install>\DLC wherever your other dlcs are). They should end up as <TW3 game install>\dlc\dlcxxx ( never <TW3 game install>\dlc\dlc\dlcxxx !). TW3MM would do this automatically for you.

Your mod's mod menu file xxx.xml would have to end up as <TW3 game install>\bin\config\r4game\user_config_matrix\pc\xxx.xml. Again, TW3MM would do this automatically for you. If you happen to have more mod menus tham what can fit on the mod menu list you can easily edit & group mod menus together into subgroups yourself using something like notepad++, example: 1-> 2 (that mod menu was placed in a "combat" subgroup, example from Menu Strings).

If your mod has custom keybinds you probably have to add them to your <My Documents>\The Witcher 3\input.settings file using some editor like notepad++. Once more, TW3MM will usually do this automatically for you.

After your mod's files & folders are in the right places you need to run patched Script Merger and merge any conflicting files that can be merged together (that means both .ws scripts and .xml bundled files).

Sadly, not all mods will automatically merge together, most probably won't (though all LEGO merge automatically with each other, obviously), but some unresolved conflicts can be solved with a little manual help:

nV1kEIS.png

The bottom half is the output/result of your merge, the yellow <Merge Conflict> line is the conflicting line that SM can't figure out automatically. 
Right click on the merge conflict and you get some simple options:

XmCXTKm.png
^There you picked the line from mod 2, but you can also pick the lines from both mods, in any order:

DytvD2Z.png
Or you can even write your own code in there. Of course knowing which lines to choose or how to make them work together does require you to somewhat understand what the code does. When in doubt you might try asking the concerned mod's authors & users for help in the comments sections.

However keep in mind that there's no guarantee that any 2 mods can be effectively merged together, nor is there any guarantee that 2 mods are working well together even if they merged automatically and the game seems to be running ok.

That's why to be extra safe you should carefully read each mod's install instructions to make sure there aren't any special instructions or requirements for the mod to work (some mods might require other mods to work such as the unification/community patch or shared imports) or incompatibilities, and then merge & run the game after each new mod install to make sure it's running well.

Edited by Partoutatix, 20 July 2019 - 03:59 PM.




Reply to this topic



  



Also tagged with one or more of these keywords: mod, error, script, compilation

Page loaded in: 1.074 seconds