My own created Maps make DOW crash

[ZAOS]

Good afternoon,

im experiencing some troubles with putting my newly created map to the test. I`ve created some earlier maps in the Mission Editor by normally choosing for w40 for objects, decals, detail map edit and such and could use them without DOW crashing.

(as you all know, you can choose when starting with creating a new map, between w40k, wxp or any of the other installed mods you have)

Now i`ve tried to mod a map with the DOW-WA (wxp) objects, decals, detail map which obviously provides a wider range of usable "scenery" to create an intruiging map, the only downside is, it makes DOW crash; so it just looks nice in the mission editor, but playing it is sadly not going to happen.


Now i was wondering if someone could point out what i am doing wrong. When opening this specific crashing map file in the mission editor it announces that it failed to open some folders.

* Failed to load archive `W40k\W40kDataGOTY.sga`
* Failed to open folder `WXP\Locale\english\Data`.
* Failed to open folder `WXP\Data_Shared_Textures\Full`.
*Failed to open folder `WXP\Data_Sound\Full`.

Well the list of failings is a bit longer, but i presume you get the picture. A lot of failings, probably the reason why the moment that i try to load this map in skirmish mode, the bar runs from left to the center and then suddenly the game stops and DOW crashes etc.

In the "Error Message" screen in the mission editor it mentions:

* Warning [ART]: `Strategic_Point`: WARNING -- Motion`s `capturing_raise` has an absolute modifier, has events, and does not ignore transitions.

* Warning [SDT]: Using deafult patch for races\orks\structures\damage_fire\25_damage_fire



Well that`s it and im quite new to creating my own maps otherwise i would have tried to figure this out myself.


One more thing i would like to mention; is it correct that you can only install the Mod Tools when you have not yet installed patches beyond 1.41 ?

Because, Mod Tools refused to install itself while my patch was up to 1.51, so i had to remove WXP and reinstall the patches up to 1.41 and then Mod Tools could be installed and afterwards i installed WXP again with the extra patches (so i can use DOW Pro 1.56)

SINcerely,
Zaos

And thanks in advance for the possible help :thumb:

[Finaldeath]

You are probably only saving it in the totally wrong folder. Save in the WXP\Data\scenarios\mp folder.

Those errors you describe are all perfectly normal - they are just slight warnings, the first lot always happens.

[ZAOS]

Save in the WXP\Data\scenarios\mp folder.

That goes without saying, but even this does not prevent the crash.

[Finaldeath]

warnings.log file please then

[ZAOS]

I could copy paste it here, but i have begun with another Map since this couldn`t be used and i presume that the warnings.log has been altered due to the beginning of a new map and trivial errors like that i have placed 2 objecs on the same spot.

Anyway, i`ll just post it, perhaps you can make more of it

20:51:03.13 MATHBOX -- Version=5, Cpu=unknown:f=6,m=13, Mode=SSE
20:51:03.15 FILESYSTEM -- filepath failure, path does not exist 'Engine\Locale\english\Data'
20:51:03.15 ME -- Warhammer Mission Editor, Build 84050.63986
20:51:07.15 ME -- Loading scenario C:\Program Files\THQ\Dawn of War\W40k\Data\scenarios\mp\Annullo Imperiosus (2).sgb
20:51:07.22 MOD -- Initializing Mod w40k, 1.0
20:51:07.26 MOD -- Warning: Failed to load archive 'W40k\W40kDataGOTY.sga'
20:51:07.27 MOD -- Warning: Failed to open folder 'W40k\Locale\english\Data'.
20:51:07.27 MOD -- Warning: Failed to open folder 'W40k\Data_Shared_Textures\Full'.
20:51:07.27 MOD -- Warning: Failed to open folder 'W40k\Data_Sound\Full'.
20:51:07.27 MOD -- Warning: Failed to open folder 'W40k\Data_Whm\High'.
20:51:07.94 SPOOGE - Driver[Dx9 : Hardware TnL] on adapter[0], version[4,32]
20:51:08.24 SPDx9 -- Driver Name = nv4_disp.dll Device = \\.\DISPLAY1 Desc = NVIDIA GeForce Go 7900 GTX
20:51:08.24 SPDx9 -- Driver Vendor = 0x10DE Device = 0x0299 SubSys = 0x05711558 Rev = 0x00A1
20:51:08.24 SPDx9 -- Driver Version Product = 0x0006 Version = 0x000E SubVersion = 0x000A Build = 0x210F (8463)
20:51:08.24 SPDx9 -- Driver GUID = {D7B71E3E-41D9-11CF-E757-7B2500C2CB35}
20:51:08.26 SPOOGE -- 612.00MB available texture memory
20:51:08.26 SPOOGE -- 612.00MB available texture memory
20:51:08.30 SOUND -- Initialized with sounds disabled and no files loaded
20:51:08.63 'Strategic_Point': WARNING -- Motion 'capturing_raise' has an absolute modifier, has events, and does not ignore transitions -- it may skip events!
20:51:08.65 'Strategic_Objective': WARNING -- Motion 'capturing_raise' has an absolute modifier, has events, and does not ignore transitions -- it may skip events!
20:51:08.69 TEXTURES -- 'relic_main': has texture on 'Self Illumination' channel!
20:51:08.93 TEXTURES -- 'art/ebps/environment/all/texture_share/razorwire_01': opacity channel has mode 'Texture'.
20:51:08.93 TEXTURES -- 'art/ebps/environment/all/texture_share/razorwire_01': has texture on 'Opacity' channel!
20:51:08.97 TEXTURES -- 'art/ebps/environment/urban/texture_share/powerpoles_01': opacity channel has mode 'Texture'.
20:51:08.97 TEXTURES -- 'art/ebps/environment/urban/texture_share/powerpoles_01': has texture on 'Opacity' channel!
20:51:09.01 'Citizen_Man_A': WARNING -- Motion 'thrown_long' has an absolute modifier, has events, and does not ignore transitions -- it may skip events!
20:51:09.01 'Citizen_Man_A': WARNING -- Motion 'thrown_short' has an absolute modifier, has events, and does not ignore transitions -- it may skip events!
20:51:09.01 'Citizen_Man_C': WARNING -- Motion 'thrown_long' has an absolute modifier, has events, and does not ignore transitions -- it may skip events!
20:51:09.01 'Citizen_Man_C': WARNING -- Motion 'thrown_short' has an absolute modifier, has events, and does not ignore transitions -- it may skip events!
20:51:09.16 (-77.00,-63.00) Two objects (1186, 1273) in exact same location
20:51:09.16 (-55.00,-34.00) Two objects (1197, 1198) in exact same location
20:51:09.16 (-36.00,-35.00) Two objects (1263, 1265) in exact same location
20:51:09.16 (12.00,26.00) Two objects (1451, 1452) in exact same location
20:51:09.16 (-102.00,-105.00) Two objects (1466, 1468) in exact same location
20:51:09.16 (-102.00,-119.00) Two objects (1467, 1469) in exact same location
20:51:09.16 (-108.00,-102.00) Two objects (1490, 1491) in exact same location
20:51:09.16 (-110.00,-102.00) Two objects (1492, 1493) in exact same location
20:51:09.16 (-110.00,-102.00) Two objects (1492, 2673) in exact same location
20:51:09.16 (-110.00,-102.00) Two objects (1493, 2673) in exact same location
20:51:09.16 (-112.00,-102.00) Two objects (1494, 1495) in exact same location
20:51:09.16 (-92.00,-110.00) Two objects (1496, 1500) in exact same location
20:51:09.16 (-92.00,-112.00) Two objects (1497, 1501) in exact same location
20:51:09.16 (-92.00,-112.00) Two objects (1497, 2679) in exact same location
20:51:09.16 (-92.00,-114.00) Two objects (1499, 1502) in exact same location
20:51:09.16 (-92.00,-112.00) Two objects (1501, 2679) in exact same location
20:51:09.16 (-17.00,-110.00) Two objects (1512, 1660) in exact same location
20:51:09.16 (-17.00,-120.00) Two objects (1524, 1534) in exact same location
20:51:09.16 (-74.00,-3.00) Two objects (1561, 2574) in exact same location
20:51:09.16 (12.00,-130.00) Two objects (1632, 1638) in exact same location
20:51:09.18 (-177.00,-97.00) Two objects (1789, 1790) in exact same location
20:51:09.18 (-177.00,-97.00) Two objects (1789, 1792) in exact same location
20:51:09.18 (-177.00,-97.00) Two objects (1790, 1792) in exact same location
20:51:09.18 (-177.00,-137.00) Two objects (1794, 1795) in exact same location
20:51:09.18 (-177.00,-137.00) Two objects (1794, 1796) in exact same location
20:51:09.18 (-177.00,-137.00) Two objects (1795, 1796) in exact same location
20:51:09.18 (-166.00,-103.00) Two objects (1804, 1805) in exact same location
20:51:09.18 (-225.00,-97.00) Two objects (1817, 1818) in exact same location
20:51:09.18 (-225.00,-97.00) Two objects (1817, 1819) in exact same location
20:51:09.18 (-225.00,-97.00) Two objects (1818, 1819) in exact same location
20:51:09.18 (-226.00,-137.00) Two objects (1822, 1823) in exact same location
20:51:09.18 (-226.00,-137.00) Two objects (1822, 1826) in exact same location
20:51:09.18 (-226.00,-137.00) Two objects (1823, 1826) in exact same location
20:51:09.18 (8.00,98.00) Two objects (2249, 2256) in exact same location
20:51:09.18 (8.00,104.00) Two objects (2250, 2255) in exact same location
20:51:09.18 (25.00,114.00) Two objects (2263, 2602) in exact same location
20:51:09.18 (-49.00,114.00) Two objects (2338, 2959) in exact same location
20:51:09.18 (114.00,19.00) Two objects (2356, 2376) in exact same location
20:51:09.18 (-47.00,111.00) Two objects (2371, 2979) in exact same location
20:51:09.18 (-63.00,-131.00) Two objects (2575, 2653) in exact same location
20:51:09.18 (-67.00,76.00) Two objects (2970, 2983) in exact same location
20:51:09.18 (-82.00,109.00) Two objects (3006, 3026) in exact same location
20:51:09.18 (-20.00,80.00) Two objects (3116, 3118) in exact same location
20:51:09.18 (-29.00,80.00) Two objects (3124, 3126) in exact same location
20:51:09.18 (-52.00,168.00) Two objects (3167, 3473) in exact same location
20:51:09.18 (165.00,-146.00) Two objects (3723, 3728) in exact same location
20:51:09.19 (148.00,-163.00) Two objects (3726, 3860) in exact same location
20:51:09.19 (8.00,237.00) Two objects (3931, 4117) in exact same location
20:51:09.19 (-88.00,-121.00) Two objects (4224, 4225) in exact same location
20:51:09.19 ME -- Scenario loaded successfully
20:51:09.22 Using default patch for races\orks\structures\damage_fire\25_damage_fire
20:51:12.08 Using default patch for environment\sp\m02\pumphouse\pump_house_run

If this isn`t what you were looking for, i will begin a new map with the WXP samples and if the problem reoccurs again, i shall immediately copy paste the warnings.log file in this folder

[Grabnutz]

what are the objects that are all in the same place? (use the "error find" thing in the ME to cycle through objects associated with the errors.
If its an ambient FX object or something that you have that many of, it could cause the crash...

[Titler]

How do you feel about uploading a version of the map which is causing your crashes, so we can test it on our own installs...?

Dont worry about the vast majority of those errors... The "thrown_long" etc are inherant in the placing of civilians on the map, no idea what they mean but they don't cause crashes on my map that uses them. Likewise the two objects in the same place (although it is neater to remove as many as possible, one or two of the errors may not actually be directly overlapping).... The only one I don't recognise is the ART errors, which appear to be indicating you've a custom texture on the map which hasn't been created properly (Opacity channel doesn't have an alpha image but a full color image in it). Try taking out the textures "razorwire_01" and "powerpoles_01" and see if that helps

[ZAOS]

what are the objects that are all in the same place? (use the "error find" thing in the ME to cycle through objects associated with the errors.
If its an ambient FX object or something that you have that many of, it could cause the crash...

I might have found the problem. When i tried to use the CTRL C and then CTRL V function to copy paste certain objects it works without a problem, but then when i selected a whole lot of buildings, including ambient FX and copy pasted it, which doesnt always seem to work, it copy pasted it perhaps a million times, its ludicrous.

So, if there is a possibility that DOW might crash because of too much ambient FX objects in one place, to overkill of objects in one place due to a malfunction in the copy paste method will have probably been the "bug" in my soup

How do you feel about uploading a version of the map which is causing your crashes, so we can test it on our own installs...?

Well, that map for sure won`t work, im positive, though i have just created another map, and perhaps i`ll upload that one, if you are interested.

[ZAOS]

For those that want to test my map:

Zaosss - Annullo Imperiosus

[Panama]

I did'nt have a problem with it. Worked fine.

[Finaldeath]

Based on Panama's report, reinstall the game entirely and patch to 1.51 then install the mod tools again.

Although I am sure you did this already, right?

[ZAOS]

Based on Panama's report, reinstall the game entirely and patch to 1.51 then install the mod tools again.

I can`t install Mod Tools when i have it patched up to 1.51.

I have to install it without any patches for Winter Assault.

But now again, i have some different type of probs.

The current map i am working on, some things had to be changed, so i changed them, saved the map, closed it, load it in a skirmish mode, come to the conclusion that strangely enough nothing has been altered, then reopen modtools again, loods the file and al my alterations are gone...

yay. Is this normal for this program to be so buggy?

[Finaldeath]

It seems that its your localised problem, please please please reinstall your game and the mod tools.

[Titler]

The current map i am working on, some things had to be changed, so i changed them, saved the map, closed it, load it in a skirmish mode, come to the conclusion that strangely enough nothing has been altered, then reopen modtools again, loods the file and al my alterations are gone...

These alterations... they wouldnt happen to be a vertical alignment would they? Did you open the map, move the items vertically, then save, and in game they were back in the original position? If this is what you are refering too, it's a very simple explanation... The items are on "Relative To Terrain", and whilst they'll stay visibly where you stick them upon saving, once the game loads, they'll leap back into their Relative position. The way to fix this is re-open the map, select all the items, and click "Adjustable". Move them out and back into position to make sure they are toggled over to "Adjustable", then resave again. They'll now stay where you put them. It's not a bug as such, you've simply got tagged incorrectly.

If it's something else however, I have no idea as yet. You'll have to explain more. However the mod tools, whilst not perfect, aren't as bugged as you seem to be experiencing, as evinced by the number of maps that have been made within 10 days for the competition. You simply need to learn it's little idiosyncronicities and how to work around them.