I've almost finished a text based graphical debug that doesn't actually attach civilian debug balls to any units, but shows suppression status with text floating near each unit. I will release the next TPWCAS with it as an option. So you'll be able to select either no debugging, text based, or full pretty balloons. Hopefully everyone will be happy then.
Also, Professor Ollem has just about hit the MP and Dedi nail on the head, so an experimental build of MP TPWCAS will be released shortly also.
Isn't a case of can't be bothered but constraints on time I have available to test. I noticed what I thought might be a problem and, because others want to use coslx and it's been pointed out that there might be conflicts between mixing it and other mods with tpwc, asr etc, I thought I'd share my observations on here for others to investigate further if so inclined. Remember I'm not trying to pick holes in coslx and I've stressed a number of times already that the problem I've seen is with tpwc debug enabled only. coslx with or without wounds included with tpwc debug disabled works fine.
Hmm, I think you read my post as harsh, in retrospect it might seem so as it was rather terse - not my intention, apologies if I inadvertently offended you.
Actually I lied - I have in fact run a few more tests as I was puzzled why the civ count shot up so abruptly - there are only 12 -15 or so civ units spawned in that mission AFAICT, It's odd that even with debug off the count goes up (but still stabilises). Same happens with no COSLX, just that the count is higher with that running as well.
Not terribly well controlled experiments, I lacked the time & concentration to set up a proper test mission; I may do that as I'm puzzled what it is counting. It isn't dead bodies; I reduced the recycle bin max to 20 & got similar figures to when it was 200.
IIRC all sorts of things including a lot of inanimate objects are classed as civs. Maybe it's something unobvious like dropped weapons - if you're using vanilla CO SLX_wounds the count of those will go up over time.
@tpw: great, looking forward to it. Colours don't show up too well through NVGs
I'm using COSLX (all of it), ACE, ASR_AI and TPWC_AI and I haven't noticed any real problems except that dead bodies rarely behave a bit funky but that's probably a COSLX issue.
bDetect start hint now correctly not displayed if TPWCAS hint is not displayed.
Courage is only decreased if there are nearby friendly casualties.
bDetect 0.67.
The main change is floating text debugging, which might help those people who'd like visual debugging but are experiencing issues with balls registering as civilians. Both kinds of debugging are on by default.
Even though these have been SP releases, I have been able to test solely on my dedi. For the majority of time it works reasonably well. A full MP variant will be lovely.
I reckon that I will still get a slight slowdown as I normally run with 300-400AI most of the time
Even though these have been SP releases, I have been able to test solely on my dedi. For the majority of time it works reasonably well. A full MP variant will be lovely.
I reckon that I will still get a slight slowdown as I normally run with 300-400AI most of the time
Keep up the good work gents !
You know how I keep saying Ollem and Fabrizio are magicians? I mean that metaphorically. If you could run 400 units without slowdown, then they'd have to be actual magicians....
You know how I keep saying Ollem and Fabrizio are magicians? I mean that metaphorically. If you could run 400 units without slowdown, then they'd have to be actual magicians....
Thanks, but Fabrizio is the real magician - I'm just the assistant ;-)
A few quick tests - same missions, same addons as before:
- the text debug clashes badly with CO SLX_wounds, I'm guessing it's the name-labelling of the wounded ally markers. System graunches to a halt, errors like: Spoiler:
Code:
Cannot create video memory surface DXT5,1024x1024 (size 1398096 B), Error 8876017c
Virtual memory total 2047 MB (2147352576 B)
Virtual memory free 1271 MB (1332752384 B)
Physical memory free 1075 MB (1127419904 B)
Page file free 3167 MB (3321188352 B)
Process working set 522 MB (547540992 B)
Process page file used 529 MB (555712512 B)
Longest free VM region: 361562112 B
VM busy 1023528960 B (reserved 162566144 B, committed 860962816 B, mapped 60616704 B), free 1123823616 B
Small mapped regions: 15, size 86016 B
VID: alloc 903634668, limit 2147483647, free: local 0, nonlocal 61067166, DX9 60817408, virt. 1333211136
Error: Failed to create surface texture (ca\structures\data\plastic\plastic_grey_old_nohq.paa:0)
Debug balls work OK, but twice also had some video memory surface errors (but recovered after a flush). The tell-tale is suddenly getting a black screen with "Receiving...", both times on switching from optics to normal view. Also noticed when I turned them on that map unit markers were now mostly triangles (with or without SLX running) & a few allies had red triangles.
Without SLX in Trial by Fire (2of 3 runs) the chopper didn't land, it headed inland; Once it shot up the ZSU truck then landed, once it just kept circling around shooting (badly!) at anything enemy, & never landed. With SLX it merely fires at the truck as it comes in to land.
In a couple of missions - "Pinned Down" & a port to Podagorsk of the latest Flashpoint mission - with & without SLX, & a single run of "Pinned Down" without asr_ai or SLX (so only CBA, TPW_LOS & OKT_noblur running) I got intermittent error messages about aiming shake:
Code:
Error in expression <"aimingshake",_newshake];
_unit setskill ["courage",_newcourage];
};
>
Error position: <setskill ["courage",_newcourage];
};
>
Error Type Any, expected Number
File tpwc_ai_suppress_207\tpwcas_decskill.sqf, line 47
I had similar results with the script version & the PBO. Also happened once or twice with all debugging off in one test.
I'll have a hack at the SLX_Wounded.sqf in ORC_SLX_wounds to see if I can disable the wounded-ally marker-naming without buggering up the whole thing. The naming is fairly pointless anyway (except maybe in a large MP).
If something is conflicting with map markers I should probably look at one or two HC missions as well.
I'll run some more methodical tests tomorrow - just CBA & TPWC AIS207, then add in the others one by one.
HOME 
Originally Posted by tadanobu
- I have in fact run a few more tests as I was puzzled why the civ count shot up so abruptly - there are only 12 -15 or so civ units spawned in that mission AFAICT, It's odd that even with debug off the count goes up (but still stabilises). Same happens with no COSLX, just that the count is higher with that running as well.
