I set up a side, and when I munge, i get a 1 kb lvl file, with nothing in it.
Here is the munge_log Here is the side req, and then the unit req The unit name is "scout2_inf_sniper", yet here is the scout2.lvl file. And for some reason, there is a file called scout2.lvl, but the full extension name is scout2.lvl.req, req being the file type.
In that there is what do I need to do?

thanks

fiddler_on_the_roof wrote:I set up a side, and when I munge, i get a 1 kb lvl file, with nothing in it.
Here is the munge_log

Code: Select all

ERROR[levelpack req\impscout_inf_sniper.req]:Expecting bracket, but none was found.
File : munged\pc\imp_inf_scout.model.req(1)...

ucft <--
ERROR[levelpack req\impscout_inf_sniper.req]:Expecting bracket, but none was found.
File : munged\pc\imp_inf_scout.model.req(1)...

ucft <--
 [continuing]
   2 Errors    0 Warnings

ERROR[levelpack scout2.req]:Expecting bracket, but none was found.
File : munged\pc\impscout_inf_sniper.lvl.req(1)...

ucft <--
ERROR[levelpack scout2.req]:Expecting bracket, but none was found.
File : munged\pc\impscout_inf_sniper.lvl.req(1)...

ucft <--
 [continuing]
   2 Errors    0 Warnings

Here is the side req, and then the unit req

Code: Select all

ucft
{
    REQN
    {
        "lvl"      
        "impscout_inf_sniper"
    }
}

Code: Select all

ucft
{
    REQN
    {
        "class"
        "scout2_inf_sniper"
    }
}

The unit name is "scout2_inf_sniper", yet here is the scout2.lvl file.

Code: Select all

And for some reason, there is a file called scout2.lvl, but the full extension name is scout2.lvl.req, req being the file type.
In that there is

Code: Select all

ucft

what do I need to do?

thanks

try putting the same name for all files ( impscout_inf_sniper )

All the files have the same name(scout2_...), meaning that the scout2.req has scout2_inf-sniper (the name of the unit, and the unit req), the unit req is called scout2_inf_sniper, and the unit is called scout2_inf_sniper, all the names are set up correctly, yet still no proper lvl file.


thanks

fiddler_on_the_roof wrote:All the files have the same name(scout2_...), meaning that the scout2.req has scout2_inf-sniper (the name of the unit, and the unit req), the unit req is called scout2_inf_sniper, and the unit is called scout2_inf_sniper, all the names are set up correctly, yet still no proper lvl file.


thanks

See that in red? Is that a typo? Cause if it's not, there's your problem.

Fiodis wrote:

fiddler_on_the_roof wrote:All the files have the same name(scout2_...), meaning that the scout2.req has scout2_inf-sniper (the name of the unit, and the unit req), the unit req is called scout2_inf_sniper, and the unit is called scout2_inf_sniper, all the names are set up correctly, yet still no proper lvl file.


thanks

See that in red? Is that a typo? Cause if it's not, there's your problem.

Yeah, that is a typo on my part, in this message.

did you try setting the unit's .odf name and unit's .req name to be the same?

They are the same, everything is under teh name of scout2_...

I'm guessing you're looking at the build files there. (Also, I'm assuming the actual source files are setup correctly.) If so, your munge just failed. Clean, remunge, and it should be fine.

I'll try, but I don't think it will work, because I've done it before. Also, if it helps, the unit that is in the side, just recieved a rep_sniper_cape, via hex-editing, don't know if that matters though.

VM is a little glitchy, so manually clean and remunge, if a regular clean fails. The model change won't matter to the munge, so long as it was edited correctly. In fact, if there was a problem with the model, you'd likely find it in the log.


That lvl.req file is a file that's copied over to the addon directory, right? If so, you don't need that file, as far as I know.

Ok, yeah, the only thing in the mungelog is I don't know why it comes up with this, because to my knowledge, there is nothing wrong with the 2 req files.

It comes up with those errors if there is a problem with the msh as well.
It can't complete what it needs to do so it can't write those files properly and therefore create an error.
You mentioned hexediting in a cape. Put a normal (non editied) unit msh reference in the odf file instead, then clean and remunge the side.
That will tell you if it is the modified msh or if it is something else.
If it fixes the problem and you can play as the imp_inf_scout then try and redo your hexedit.

FragMe! wrote:It comes up with those errors if there is a problem with the msh as well.
It can't complete what it needs to do so it can't write those files properly and therefore create an error.
You mentioned hexediting in a cape. Put a normal (non editied) unit msh reference in the odf file instead, then clean and remunge the side.
That will tell you if it is the modified msh or if it is something else.
If it fixes the problem and you can play as the imp_inf_scout then try and redo your hexedit.

Yeah, it looks like it was the hex-edit, so
re-doing hex-edit (crosses-fingers)...

thanks