Suggested Option: Alternative army setup display. - Page 2

Gandalf Parker · #11 March 8th, 2007, 04:34 PM

Double Click might have an upper limit but I suspect that its not far from the upper limit of what you can assign to a commander anyway. Do we really need doubleclick to pick up more than 255 of something so you can assign them to one unit? (I dont know if thats the limit)

Edi · #12 March 8th, 2007, 04:36 PM

Meglobob, last I checked, your name wasn't Taqwus.

He was asking the question on sorting stuff. He's also right about the units being sorted by individual ID.

Edi

Taqwus · #13 March 8th, 2007, 06:16 PM

Oh, on the wounded/exp thing I was referring to the hypothetical state where stacks where implemented. It's all fine and dandy to say 'here are X gazillion units of the same type represented by an icon + number', but in such a case it may still be useful to be able to break it down by xp/affliction status. That way, the wounded and greenhorns can, er, prove their valor on the front line, if that's what's needed.

Edi · #14 March 8th, 2007, 06:18 PM

Ah, okay. My mistake then.

Cor · #15 March 8th, 2007, 06:50 PM

I have also run into the double click problem, I just got a newer beefer PC and I run into much less, So i wonder if its a hardware limitation?

Anyway, this feature would be the coolest thing since sliced bread.

Edi · #16 March 8th, 2007, 07:33 PM

Sliced bread is severely overrated.

Seriously, it has probably something to do with system memory and processor capacity limitations. I'm running a top end Core 2 Duo system with nearly the latest kit as of last September and turn resolution can take a frighteningly long time in e.g. 8 nation Cradle games. Haven't had problems with the masses of units, but my old machine (a Y2K vintage Celeron 500 system that burned out in July) would have simply collapsed under this sort of load. It'd be nice to know the hardware specs of the people who are experiencing this bug issue, it could help narrow it down.

Ballbarian · #17 March 8th, 2007, 08:07 PM

Well... My focus wasn't so much on the double click, but:
WinXP
1.3ghz AMD
512mb Ram
NVIDIA GeForce FX 5700LE w/ 256mb DDR graphics card

Running very lean & mean for such low specs. Actually, I get better performance with my low end optimized machine than we do with the 2&3ghz machines at work (but the users have a bad habit of running every piece of crud background process that they can find on the net, or install off of their HP printer cd.

)

UPDATE:
Just did a quick test and the bottleneck appears to be tied to the CPU. The dom3 process idles around 43% on the main screen (large map with lots of armies), then upon entering the Army Setup screen, it leaps to 99% and I lose double click in dom3.

Sombre · #18 April 16th, 2007, 12:57 AM

This idea is excellent and it would probably help people a lot if it were implemented. It doesn't seem like it would be ridiculously hard to do either.

Should we have a thread where we can store all the best suggestions - the ones the community agrees are possible for the devs (or reasonable, within a patch) and are helpful?

People could then weigh in on what the most important change suggested is and maybe the devs would have a better idea of what their fans would like. The devs could also respond telling us if a suggestion is too far fetched or hard to implement.

Loren · #19 April 16th, 2007, 03:51 PM

Quote:

Gandalf Parker said:
Double Click might have an upper limit but I suspect that its not far from the upper limit of what you can assign to a commander anyway. Do we really need doubleclick to pick up more than 255 of something so you can assign them to one unit? (I dont know if thats the limit)

There's no such limit. I've picked up over 500 units with doubleclick.

The problem isn't with what you can pick up, it's with what you're picking it up from. If there are too many units in the garrison you can't doubleclick it, period.

I think I know what's going on here. The more units you have in the garrison the closer together they are. I think the doubleclick failure is due to the units getting closer together--if they're packed too tight it won't work. Note that this explains the poster who found the limit went up when he got better hardware--he probably was running in a higher video mode.

It's a pain with any race that has freespawn.

Ballbarian · #20 April 16th, 2007, 05:13 PM

I will repeat:

Quote:

Just did a quick test and the bottleneck appears to be tied to the CPU. The dom3 process idles around 43% on the main screen (large map with lots of armies), then upon entering the Army Setup screen, it leaps to 99% and I lose double click in dom3.

It is possible that increasing video memory/processing could take some of the stress off of the CPU, but I still firmly believe that the loss of double click is a result of overloading the CPU.