Help needed with map upload (solved)

[seero]

Hi mappers.

I've always had troubles with getting my maps in vault but this time it's killing me.. Could anyone find out the reason why the attached map won't load properly in vault? It just appears as a blank map that cannot be downloaded.. Map version and screenshot are updated but map itself just wont load. I uploaded new version from one of my old maps and it worked well so currently my client version should work properly. I've tried to copy scenario and script files from working map and almost everything that i ever could imagine but it just wont work.

map files: https://1drv.ms/u/s!AgnFbmAipoN0hZ1q6uaJeixcV1ZLLQ

[speed2]

how did you upload the previous 199 versions?

[seero]

With Downlord's 0.7.7.2-apha. No error messages or anything during the upload and i can play that map without any errors in FAF but it just wont appear properly in vault.

[svenni_badbwoi]

Hey, I had a quick look at the scenario file. If that is the upload version you should remove all ".vXXXX" from file and folder to prevent this from happening and try again.
The reason behind that: Upload process was changed to make versioning simpler I believe. Versioning depends on "map_version= X" and will be created/writen in files via upload.

But since you were able to update a different map, I'm not sure if that will help you.

[Wolfram_74]

I think the problem is a script file. Try to change your Panama Bay_script.lua file to my example. I have 0.7.7.2-alpha Downlord version too and my maps are uploading correct.

It looks like you missed some text:
ScenarioFramework.SetPlayableArea('AREA_1' , false)

[CookieNoob]

Code: Select all

ScenarioFramework.SetPlayableArea('AREA_1' , false)

this is not necessary in the script file, except you want to restrict the playable area to some smaller area. This command is not needed for most of the maps. The content of the scriptfile is for uploading purposes completely irrelevant.

The only things that I can imagine to cause problems are
1) some mistake in the scenario file (i.e. the team configuration is called "Standard" instead of "standard" or...), this type of error can lead to the upload not working (gives an error message)
2) some mistakes in the scmap file (i.e. the editor set the colors for the minimap to white instead of the appropriate colors...), this type of error could cause your problem
3) some naming issues, (i.e. the map file has a different name than the one specified in the scenario file), this isnt the case here
4) some mysterious magic

did you create the map with ozonex editor? if yes: in which format did you save it? you could try to save it with the original editor again

[seero]

Thanks for replies. Im using original supcom map editor. Ive taken script and scenario files from working map so for me seems that there is some dark magix in scenario or save file.

[seero]

Hey, I had a quick look at the scenario file. If that is the upload version you should remove all ".vXXXX" from file and folder to prevent this from happening and try again.
The reason behind that: Upload process was changed to make versioning simpler I believe. Versioning depends on "map_version= X" and will be created/writen in files via upload.

But since you were able to update a different map, I'm not sure if that will help you.

This was the actual problem. Apparently you cannot name folders any more (it used to work since i was born??). Just keep folders name without version suffix and increase revision in scenario and it works. I dont know why my old map worked even it was revised with old style.. perhaps because the original was uploaded in good old times.


Thanks for helping.

EDIT: The uglies thing in this case is that when you upload it to vault and download it again, it has added those freaking version numbers to file folder, and next problem is ready:
/viewtopic.php?f=53&t=15995