Editing minefields

[DOCUP]

How do I add a minefield at a base that doesn't have one?

[Ian R]

There was a thread where it was indicated that starting minefields are created by the exe, the determinants being the base's port size, and possibly fortification level. Maybe just port size.

[Dili]

Yes it seems to be hardcoded. Maybe you can make a minelaying TF with some minelaying barges in that ports that miss mines to lay the mines in first day.
A bit of search it seems that ports 5 and over have mines: starting at 250.

Edit:
So port

5=250
6=300
7=350
8=400
9=450
10=500

The caveat is 4 size ports some have 200 mines but others have nothing, i have checked naval support level but i didn't find any consistent number difference to explain it by naval support.

[US87891]

ORIGINAL: DOCUP
How do I add a minefield at a base that doesn't have one?

If you want to add a minefield at the start, use the mine column in WitploadAE. It does not appear in the editor.

Matt

[Dili]

Thanks Matt.

[Ian R]

ORIGINAL: US87891

ORIGINAL: DOCUP
How do I add a minefield at a base that doesn't have one?

If you want to add a minefield at the start, use the mine column in WitploadAE. It does not appear in the editor.

Matt

Wish I could.

[DOCUP]

Thanks guys. I don't know if I should try the WitploadAE.

[Dili]

Ian R did you tried compatibility settings in exe. properties? If not find an emulator.


I have a subsequent question, what is the mine model that is choosen by default?

[US87891]

ORIGINAL: Ian R
Wish I could.

It is an old DOS shell, but it runs ok. It is just very literal about the invocation and doxology. You have to launch from the directory where it’s at.

Example: I made a top level folder C:\AE. Made a folder underneath that C:\AE\Scen28. Put the scen28 files in there as well as a copy of WitploadAE.exe.

When I want to play, launch the command prompt. It starts at the default directory:
C:\Users\Yourname>
type cd\ <enter> (no spaces) it then shows:
C:\>
type cd \ae\scen28 <enter> (there’s a space after cd) it then shows:
C:\AE\Scen28>
then type either:
witploadae /e /s28 <enter> if exporting, or just
witploadae /s28 <enter> if importing

no muss, no fuss, no worrying about what files are in what directory and having to go looking or typing long command strings. Actually, I have a DOS batch file that gets me to the right place, but the manual method is pretty easy.

Hope this works for you

Matt

[Ian R]

It doesn't run off an NT environment short cut in any compatibility mode.

It doesn't run off a dos command prompt in the run box.

It doesn't run in an emulated dos environment with dosbox, (witploadAE.exe is an illegal command on the mounted dos drive)

In short, it doesn't run on my computer doing any of that.

I'm open to suggestions.

[Ian R]

ORIGINAL: US87891

ORIGINAL: Ian R
Wish I could.

It is an old DOS shell, [snip instructions]

Hope this works for you

Matt

Thank you, that worked, after I transferred things to a nice simple sub directory C:\scen. I then got a successful csv file dump.

Judging by the error messages in dosbox, the problem starts with the default install directory being (in my case) C:\matrix games. Doesn't recognise anything after the space.

[GaryChildress]

ORIGINAL: US87891

ORIGINAL: DOCUP
How do I add a minefield at a base that doesn't have one?

If you want to add a minefield at the start, use the mine column in WitploadAE. It does not appear in the editor.

Matt

Mine column? Is that in the stock game when you use WitPLoadAe or is it something added in a patch? I don't see it. [&:]

[cardas]

Yeah, I'm not aware of any mine column either. There isn't any column labelled that way in the locations .cvs created by the versions of witploadAE that I've tried.

[US87891]

Hi

column Q.

[cardas]

Yep, after your post I double checked which witploadAE I was actually using. Somehow I've managed to end up with three versions. One old enough that it output neither the secondary attributes for devices nor the "mine" field in the locations .csv (i.e. fields that can't be edited by the standard editor), one a bit modern that does export/import those secondary device attributes but doesn't export/import the "mines" field in the location .csv and finally one version that does all of it.

I was sure I had been using the latest version but apparently I've screwed up and didn't. Now I see the field, thanks.

[DOCUP]

So, If I go into the witploadAE, how bad can I screw things up?

[John 3rd]

Personal opinion is to NOT mess with it. Course...I am a computer idiot...

[DOCUP]

I'm right there with you John.

[Dili]

ORIGINAL: cardas

Yep, after your post I double checked which witploadAE I was actually using. Somehow I've managed to end up with three versions. One old enough that it output neither the secondary attributes for devices nor the "mine" field in the locations .csv (i.e. fields that can't be edited by the standard editor), one a bit modern that does export/import those secondary device attributes but doesn't export/import the "mines" field in the location .csv and finally one version that does all of it.

I was sure I had been using the latest version but apparently I've screwed up and didn't. Now I see the field, thanks.

What version is your cardas? i checked a bunch of csv that i have a none has the mine field.

[cardas]

Version 9.0, should be included with the latest beta of WitP:AE (in the beta folder).