14 réponses à ce sujet

[rjshae]

I recently attempted to convert a pair of
modules into a campaign. However, when I attempted to run the thing in
the game engine, it gave me the following error:

"Could not load the module. Module file might be corrupt OR it was created using a newer version of the toolset and/or game resources."

The individual modules run just file. I have MotB loaded, but I've
patched the install past that point, so I'm wondering if the toolset
patch level is mismatched with the game engine? I checked Sunjammer's
wonderful World Map Editor Tutorial for debugging hints on the Campaign
Editor, but that didn't help. As far as I can tell, everything is set
up correctly with the Campaign and the associated Modules. Does anybody have a fix for this?

[_Knightmare_]

What option are you choosing to start the game from off the main menu? Once you convert to a campaign, you need to choose New Game -> New Campaign.



Don't see why the patch level would matter here as long as the the individual modules were opened/saved in toolset since your last patch update.



Maybe check the modules' properties, are the "NX1/NX2 Required" options checked True?

[rjshae]

Yes I select New Game then New Campaign and choose my campaign from the list. IIRC, the NX1/NX2 Required check boxes are off.

[_Knightmare_]

Hmm, did you set the Start Module in the Campaign Settings?



Sorry if it sounds like I'm just guessing here - I am lol.

[c i p h e r]

FYI. I had a similar problem when not setting the "start module" correctly. Make sure your module name or directory (depending on what you use) has no spaces in it.

[rjshae]

Yes I did set the Start Module in the Campaign Settings, but I'm not sure if it had spaces in the name. I'll check tonight. Thanks.

[rjshae]

The only spaces I have is in the Campaign's Display Name. The campaign name and module names all use underscores as separators.

[c i p h e r]

If you patched with the updater, toolset and game should both be updated. If you were able to play the module before, then it has something to do with your setup/ campaign settings.

Modifié par ç i p h é r, 03 août 2010 - 06:19 .

[rjshae]

Yes. I'll just have to keep tinkering then. Thanks for the help.

[dunniteowl]

List of Dumb Questions:
Does your start module entry area have the start location in it?
Is there something in the Modules sections that should have been ported to the Campaign Section?
Do you have a 'backup' or older version in the same general path as the one you're wanting to run?

They don't come much dumber than that, I'd suppose. After all, I'm asking them.

dunniteowl

Modifié par dunniteowl, 04 août 2010 - 05:42 .

[rjshae]

dunniteowl wrote...

List of Dumb Questions:
Does your start module entry area have the start location in it?
Is there something in the Modules sections that should have been ported to the Campaign Section?
Do you have a 'backup' or older version in the same general path as the one you're wanting to run?

They don't come much dumber than that, I'd suppose. After all, I'm asking them.

dunniteowl

Not a problem; I appreciate any helpful insights you can provide.

Yes the start module has a start location. I'm able to run the start module just fine by itself.

None of the module scripts and blueprints have been ported into the campain sections. At present they're stand-alone and I'm trying to join them by creating a campaign.

I do have backup versions of the modules with a '_backup' suffix.

Modifié par rjshae, 05 août 2010 - 05:06 .

[Tonytobinus]

rjshae, I started having the same problem this morning, and was unable to fix it by the time I had to head out for work. I'm going to keep tinkering with it once I get home, and if I find anything I'll let you know.

[rjshae]

Thanks. I hope it's not a patch problem.

[Tonytobinus]

I don't think it is a patch problem. If anything, I'm worried that it is an OS problem (a slightly unfounded concern, but I am running on Windows 7, which has given my Neverwinter problems in the past). However, the most likely answer is that both of us are just using the wrong settings somewhere. I know, for example, that my module name has spaces in it. That might fix it for me (I hope). Either way, we can compare notes a little more thoroughly when I'm back behind a computer that has the toolset installed on it.

[Tonytobinus]

Hey, rj. I just got mine working. In my case, it was the spaces. Here's what I suggest you try:



Don't even use underscores as placeholders. Just flat out make it one word. If it helps, capitalize the first letter of each word so it is a little easier to read, but try that for all the following fields:

Module Properties: Name, Tag

Change the file name itself to one long word. Since you're running this as a campaign that won't be an issue.

in the Campaign Editor: the Display name can have spaces, the Name is just one big word.

Add your module (again, this file should have no spaces in it)

Set the starting module. Do not put ".mod" at the end of it.



Give that a try.