New! v1127 Public Beta Available

[RangerJoe]

I had mentioned that railroad issue before so it could be fixed. There are other issues that need to be fixed, things adjusted, and/or notes made about them.

[Meaneye]

Multiple damaged ships in port (none currently in repair). Go to repair screen, put 1 DD in pierside repair. Click the "put all ships in pierside" button. Take a CL that was not in repair before but is now in pierside because of said button press back out of repair. I now have to wait 3 days to move it.

Not sure when this got broken, but it didnt work this way before AE was released.

[RangerJoe]

Multiple damaged ships in port (none currently in repair). Go to repair screen, put 1 DD in pierside repair. Click the "put all ships in pierside" button. Take a CL that was not in repair before but is now in pierside because of said button press back out of repair. I now have to wait 3 days to move it.

Not sure when this got broken, but it didnt work this way before AE was released.

Whenever a ship is put into readiness mode from pierside and/or shipyard mode, it always takes 3 days to get into the readiness mode. So unless you are doing so in the ship screen itself without leaving the ship, that is what happens. Also when you are changing repair modes, any repair % of the next point of repaired damage is reset to 0%.

[AndrewV]

Hi
I'm planning on buying a new monitor, and am considering a 4k monitor.

I have vague memories of reading the WitP:AE had problems with 4k monitors. Can anyone confirm that? Does the new Beta work correctly with 4k monitors? (I'm not planning on playing the beta version, but if the beta works correctly on 4k monitors, then the next release should also work).

[BBfanboy]

Hi
I'm planning on buying a new monitor, and am considering a 4k monitor.

I have vague memories of reading the WitP:AE had problems with 4k monitors. Can anyone confirm that? Does the new Beta work correctly with 4k monitors? (I'm not planning on playing the beta version, but if the beta works correctly on 4k monitors, then the next release should also work).

I don't have a 4K monitor but some players have mentioned getting an X resolution around 2560 (I forget what the Y resolution was). The problem is the map text which stays at the same resolution as the map - which can be too tiny to read unless you have a huge monitor or use a magnifying tool. Also, laptops are very hard to get to display high resolution.
Look through the topics in the Tech section to find discussion of high resolution.

[AndrewV]

I don't have a 4K monitor but some players have mentioned getting an X resolution around 2560 (I forget what the Y resolution was). The problem is the map text which stays at the same resolution as the map - which can be too tiny to read unless you have a huge monitor or use a magnifying tool. Also, laptops are very hard to get to display high resolution.
Look through the topics in the Tech section to find discussion of high resolution.

Thanks for the reply, but I'm not talking about a laptop. I already have a 32 inch 2560x1440 monitor. It did take a little fiddling with windows scaling options and WitP:AE command line options to get a set of options that worked for me. If I buy a 4k monitor it will be at least 32 inches and probably 43 inches, which has a fairly similar dpi to my existing 32 inch monitor, so I'm not overly concerned about small text.

I more concerned with reports like https://www.matrixgames.com/forums/view ... 0#p5112440

However, the best I could "fix" the wide screen was to 3709x1600. If I jump as much as 3710x1600 it breaks the map and puts large black areas all over the hexes.

I was hoping that maybe someone in this thread had already tested the beta with a 4k monitor, and knew whether that was still an issue.

(However now that I think about it more, it is possible that it might not be an issue anyway, since windows scaling is weird, and if you turn windows scaling up to 150%, and then tell Witp:AE to use a window of roughly -pxf2556 -pyf1400, windows will probably scale that to a window of3834x 2100 which would be a close to a fullscreen window for a 4k monitor, with WitP:AE probably drawing everything the same as 2556x1400).

[Meaneye]

Multiple damaged ships in port (none currently in repair). Go to repair screen, put 1 DD in pierside repair. Click the "put all ships in pierside" button. Take a CL that was not in repair before but is now in pierside because of said button press back out of repair. I now have to wait 3 days to move it.

Not sure when this got broken, but it didnt work this way before AE was released.

Whenever a ship is put into readiness mode from pierside and/or shipyard mode, it always takes 3 days to get into the readiness mode. So unless you are doing so in the ship screen itself without leaving the ship, that is what happens. Also when you are changing repair modes, any repair % of the next point of repaired damage is reset to 0%.

It didnt used to be this way. It used to, and still should, remember the repair status at the start of the turn so you can return to it. As I said, somewhere along the line this was broken (not saying it was broken recently). I was a playtester on the original AE. No way in hell should a ship be stuck in port for 3 days because you accidentally put it in pierside mode. And no way I would have missed this in testing.

[RangerJoe]

Multiple damaged ships in port (none currently in repair). Go to repair screen, put 1 DD in pierside repair. Click the "put all ships in pierside" button. Take a CL that was not in repair before but is now in pierside because of said button press back out of repair. I now have to wait 3 days to move it.

Not sure when this got broken, but it didnt work this way before AE was released.

Whenever a ship is put into readiness mode from pierside and/or shipyard mode, it always takes 3 days to get into the readiness mode. So unless you are doing so in the ship screen itself without leaving the ship, that is what happens. Also when you are changing repair modes, any repair % of the next point of repaired damage is reset to 0%.

It didnt used to be this way. It used to, and still should, remember the repair status at the start of the turn so you can return to it. As I said, somewhere along the line this was broken (not saying it was broken recently). I was a playtester on the original AE. No way in hell should a ship be stuck in port for 3 days because you accidentally put it in pierside mode. And no way I would have missed this in testing.

It has always been that way for me. But look at when I bought the game and joined Matrixgames . . .

[Platoonist]

It didnt used to be this way. It used to, and still should, remember the repair status at the start of the turn so you can return to it. As I said, somewhere along the line this was broken (not saying it was broken recently). I was a playtester on the original AE. No way in hell should a ship be stuck in port for 3 days because you accidentally put it in pierside mode. And no way I would have missed this in testing.

It's mentioned in the original manual on page 242 (although very briefly) that any changes in repair status may occur a delay.

Page242.jpg (19.72 KiB) Viewed 1022 times

[Meaneye]

Original version. I ran a historical 1st turn. Saved it. Put all the damaged ships in Pearl in pierside. Saved it. Put the San Francisco back in readiness. Saved it. Note, there is NO 3 day delay on the San Francisco.

Dont care what the "rules" say. I know how it used to work... I tested it. Somewhere it got broken.

ver.png (272.3 KiB) Viewed 986 times

[RangerJoe]

Well then, play with no updates.

[Meaneye]

Because fixing it to be like it SHOULD be would be too much trouble? It USED to work, Cant be that hard to make it work again.

Nope, sorry Enterprise - you cant leave port for 3 days because Nimitz goofed and ordered you to pierside today, even though the turn wasnt run (which simulates the orders being executed) he said it to his aide and that was enough to park you in port for 3 days. Sorry.

Nope - unacceptable. fix it.

Edit: The bug isnt restricted to just the set all routine. I just tried setting a damaged ship manually (without using the "set all" feature) in the current version and then manually set it back and same thing. Locked in port for 3 days.

[Zovs]

I have a 4K monitor after I did my switches no problems at all no issues.

[RangerJoe]

Because fixing it to be like it SHOULD be would be too much trouble? It USED to work, Cant be that hard to make it work again.

Nope, sorry Enterprise - you cant leave port for 3 days because Nimitz goofed and ordered you to pierside today, even though the turn wasnt run (which simulates the orders being executed) he said it to his aide and that was enough to park you in port for 3 days. Sorry.

Nope - unacceptable. fix it.
Then I guess that you are going to quit playing the game.

Edit: The bug isnt restricted to just the set all routine. I just tried setting a damaged ship manually (without using the "set all" feature) in the current version and then manually set it back and same thing. Locked in port for 3 days.

If you would read what was posted from the manual by someone else, you can see how to do it without having the ship locked up for three days. For me, that is how it always has been done.

[Meaneye]

Ok, so answerthese questions...
1) I walk through units - bases first (+ and - keys) and then naval (, and . keys). So as Im going through bases, I set the repair orders (and air, and ground, and so on and so forth). Next I go through the naval stuff and if I see I need something in a given area (say a transport near Java for example) and 'lo and behold, the only available ships I have are in pierside. Oh well, huh? Its a BUG - it NEEDS TO BE FIXED. Alright?

2) Why should a player have to work around something that I have already shown is a bug, when it can probably be easily fixed? I mean IT USED TO WORK CORRECTLY once upon a time after all (proven). If you choose to jump through the hoops you currently jump through, thats fine. Thats wonderful. You will STILL be able to play the game the way you currently do now after this bug is fixed if that is what concerns you.

3) Why are YOU so against this bug being fixed? This one I REALLY want an answer to. I mean by your own admission you have no idea of how much easier fixing this bug makes the repair portion of the game, and yet you fight tooth and nail (not to mention your smart ass comments) to preserve the bug. Why? You have absolutely no idea of what you are even fighting against. /smh

4) Is YOUR name on the box? Mine is. And I want the product that I was a part of making to function as it should. Wouldnt YOU want it to work right if YOUR name was on the box?

As for your snide comment above as far as me quitting, I quit this game long before you ever started playing it. And between countless hours of testing, and years playing after it came out, and the original game of WitP (beginning to end), and the precursor (PacWar - also beginning to end) I have MUCH more time invested in it than you do... So please climb down off your high horse. Thanks. I pointed out a bug. Nothing more. Nothing less. If you have an issue with that, I guess its you that has the problem. Have a nice day.

[RangerJoe]

Ok, so answerthese questions...
1) I walk through units - bases first (+ and - keys) and then naval (, and . keys). So as Im going through bases, I set the repair orders (and air, and ground, and so on and so forth). Next I go through the naval stuff and if I see I need something in a given area (say a transport near Java for example) and 'lo and behold, the only available ships I have are in pierside. Oh well, huh? Its a BUG - it NEEDS TO BE FIXED. Alright?

2) Why should a player have to work around something that I have already shown is a bug, when it can probably be easily fixed? I mean IT USED TO WORK CORRECTLY once upon a time after all (proven). If you choose to jump through the hoops you currently jump through, thats fine. Thats wonderful. You will STILL be able to play the game the way you currently do now after this bug is fixed if that is what concerns you.

3) Why are YOU so against this bug being fixed? This one I REALLY want an answer to. I mean by your own admission you have no idea of how much easier fixing this bug makes the repair portion of the game, and yet you fight tooth and nail (not to mention your smart ass comments) to preserve the bug. Why? You have absolutely no idea of what you are even fighting against. /smh

4) Is YOUR name on the box? Mine is. And I want the product that I was a part of making to function as it should. Wouldnt YOU want it to work right if YOUR name was on the box?

As for your snide comment above as far as me quitting, I quit this game long before you ever started playing it. And between countless hours of testing, and years playing after it came out, and the original game of WitP (beginning to end), and the precursor (PacWar - also beginning to end) I have MUCH more time invested in it than you do... So please climb down off your high horse. Thanks. I pointed out a bug. Nothing more. Nothing less. If you have an issue with that, I guess its you that has the problem. Have a nice day.

1) Not necessarily, some things that people think are bugs are features. One way to keep ships from being stuck for three days is to let them finish repairing, after all that is why players put them in pierside or shipyard repair mode. Doing so gets the newly repaired ship in ready mode immediately. The other way is to never repair ships in other than ready mode. That is your choice, which mode to use.

2) Are you sure that it is a bug? Are you sure that I have no idea of how changing one part of a computer program affects another part of the program? Maybe the three day wait is a penalty, ever think of that? How long does it take to power up a ship, remove the connections from the port facilities, plus putting the ship back together so it will actually function?

3) What makes you think that I am against getting this bug fixed? After all, taking a ship out of pierside repair mode to be instantly used is realistic, especially considering what I mentioned in 2). is it not? As far as what you are otherwise stating . . .

4) I don't care about the name on the box, since you stated that you quit the game long before I ever started playing it then you probably had nothing to do with the updates which changed many things. Those updates were before my time and this update is the only one that is happening after I bought the game. I don't know your name, just your Matrix handle. So I don't know if you printed your name on the box or if the company printed your name on the box. However, since your account started on

Tue Jun 11, 2013 8:19 pm

that means that you either were not in on the development of this game or you had one and possibly more accounts. So it is entirely possible that your previous account or accounts were banned.

As far as your experience goes compared to mine, you probably know nothing about me. There is also nothing wrong with being on a high horse, especially if you have a nice weapon like a lance, saber, or even a good mace . . .

[btd64]

Multiple damaged ships in port (none currently in repair). Go to repair screen, put 1 DD in pierside repair. Click the "put all ships in pierside" button. Take a CL that was not in repair before but is now in pierside because of said button press back out of repair. I now have to wait 3 days to move it.

Not sure when this got broken, but it didnt work this way before AE was released.

Whenever a ship is put into readiness mode from pierside and/or shipyard mode, it always takes 3 days to get into the readiness mode. So unless you are doing so in the ship screen itself without leaving the ship, that is what happens. Also when you are changing repair modes, any repair % of the next point of repaired damage is reset to 0%.

It didnt used to be this way. It used to, and still should, remember the repair status at the start of the turn so you can return to it. As I said, somewhere along the line this was broken (not saying it was broken recently). I was a playtester on the original AE. No way in hell should a ship be stuck in port for 3 days because you accidentally put it in pierside mode. And no way I would have missed this in testing.

How could you have been a playtester when you joined the forum 4 years after AE was released?....GP

[Meaneye]

Whenever a ship is put into readiness mode from pierside and/or shipyard mode, it always takes 3 days to get into the readiness mode. So unless you are doing so in the ship screen itself without leaving the ship, that is what happens. Also when you are changing repair modes, any repair % of the next point of repaired damage is reset to 0%.

It didnt used to be this way. It used to, and still should, remember the repair status at the start of the turn so you can return to it. As I said, somewhere along the line this was broken (not saying it was broken recently). I was a playtester on the original AE. No way in hell should a ship be stuck in port for 3 days because you accidentally put it in pierside mode. And no way I would have missed this in testing.

How could you have been a playtester when you joined the forum 4 years after AE was released?....GP

Simple, my account was banned for posting stuff from the devs forum on the board that showed Ian was lying to people about things that were implemented in the air system. You can probably still find the thread. My original account was yamato hugger... Recently retired and blew the dust off this thing although I did do some stuff with Bill in the early days of mods way back when but was working too much to keep putting time into it.

Is the Alemeda base force (unit 5457) supposed to be mobile and have the ability to have it HQ changed? Just asking. Not sure if that was intended.

[Meaneye]

yada yada yada

Ok, The simple explanation is that orders are not "in effect" until the turn is executed. That is, and always has been *through many iterations of this game in all its various forms going back to the Apple days of Guadalcanal Campaign (which I also have on my shelf) the way this game system has always worked.

So when I say I put a unit in pierside and then go back to it later and put it in readiness - I am NOT talking about a later turn. Ok? I mean later in THAT turn. And since "orders have not been executed" yet (ie the game turn has NOT yet been run) then it falls into the category of a "bug" not a "feature".

I understand the difference. And I posted an example above how EXACTLY it used to work. Now... you know what? It just isnt worth trying to explain it to you.

Have a nice day.

(BTW I used to train Rangers back in the 70s)

[Edmon]

yada yada yada

Ok, The simple explanation is that orders are not "in effect" until the turn is executed. That is, and always has been *through many iterations of this game in all its various forms going back to the Apple days of Guadalcanal Campaign (which I also have on my shelf) the way this game system has always worked.

So when I say I put a unit in pierside and then go back to it later and put it in readiness - I am NOT talking about a later turn. Ok? I mean later in THAT turn. And since "orders have not been executed" yet (ie the game turn has NOT yet been run) then it falls into the category of a "bug" not a "feature".

I understand the difference. And I posted an example above how EXACTLY it used to work. Now... you know what? It just isnt worth trying to explain it to you.

Have a nice day.

(BTW I used to train Rangers back in the 70s)

Hey,

I'd just like to let you know that we have a reasonably high standard of behaviour on our, usually very friendly forums.

Please avoid writing posts that imply that other posters are stupid, as these will attract warnings in the future.

Thanks,
Edmon