Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Mon Jan 12, 2015 3:00 pm Post subject:
I haven't ran into Sight issues per se. On the other hand the GapGen-Superweapons-shroud bug still happens, notsure if that falls under this.
Temporal=yes in OpenTopped IFVs doesn't crash now, but passenger doesn't fire neither. I am already fine with this outcome tho. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
Thanks for testing. Psychic Reveal in both modes now uses the same mechanism to reveal portions of the map or the entire map. That is, now the time needed depends on the number of cells affected. If full map reveal is almost instantaneous, ranged reveal cannot be slower than that. This is actually not quite true, as the ranged one might also affect cells outside the map. This case is caught, but also takes a bit of time.
MasterHaosis: The lines should not be there. Thinking about it a second time, I might have found the reason for that. Will see to get that fixed.
4StarGeneral: How do you play a game where Sight isn't used? O_o There really isn't much to test in particular. It should just work as always, but now without unnecessary work that was just slow and didn't affect the outcome.
Graion Dilach: The passenger cannot fire, because the TemporalClass is moved over to the Gunner. It is then owned by the vehicle only, and not the infantry any more. From the game POV, the first passenger is the driver, and it uses its own weapon. Thus when the IFV is firing, it's actually supposed to be the infantry firing. Maybe a better way would be to deactivate any first passenger of an opentopped gunner... _________________ QUICK_EDIT
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Mon Jan 12, 2015 9:39 pm Post subject:
AlexB wrote:
Maybe a better way would be to deactivate any first passenger of an opentopped gunner...
Certainly not. If the current state is the only option then this option is okay. That idea would completely break opentopped-gunner combination units (which I'll have around 3 in the long run, I think).
It was only a note of mine but since the crash itself is fixed, I'm happy. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
There will be another build soon, fixing the sight issue, which was a math error I introduced when optimizing.
Graion: I don't find that too obvious. If you put a GI into an IFV, the IFV changes its weapon to the GI-IFV-mode weapon. The GI himself cannot fire or it fires as the IFV (depending on point of view). If you make the Gunner OpenTopped=yes, then the IFV can fire, as well as the GI inside. Now two GI weapons are used. Same with the other IFV modes, except for Temporal: The CLEG cannot fire from inside, the weapon went to the Gunner IFV. I find it slightly unintuitive that the first passenger's weapon may fire twice.
On the other hand, it will be inconsistent anyhow, depending on whether an infantry unit is first passenger or not, because either the IFV mode or the OpenTopped weapon would be used. Whatever the solution is, it won't be perfect. _________________ QUICK_EDIT
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Tue Jan 13, 2015 12:35 pm Post subject:
The Gunner unit does not need to be an IFV. You could have a unit with a missile launcher equipped with various kind of warheads, and the crew decides the used kind based upon the unit entering into it... a GI will insist this crew use HE missiles, while a GGI AP, etc.
Or you can have a balloonhover unit with a transporter beam, a laser and a free slot, in which case, the IFV logic is only used to enable the laser instead of the transporter.
As I said, the current solution is imo the best option. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Fri Jan 16, 2015 11:15 am Post subject:
Ah yea, totally forgot this one. https://bugs.launchpad.net/ares/+bug/1395460 _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
The last build before the RC phase is now here, way too late. No new features obviously, only fixes for Ares bugs. I'm still going through the lists of commits to update LaunchPad, but I'm only halfway through. I hope this will be solved soon.
Sight issues have been resolved
[Weapon]Anim= tag now supports lists longer than 127 chars
Fixed some extended list length tags
NaturalParticleLocation parsing was broken and has been fixed
[TechnoType]DebrisAnims= has been expanded also
EMP now also disables temporal weapons
Temporals could toggle power even if that was not allowed
Disallow toggling power when a building is under the effect of EMP
Always display the power off animation when the building is shut down
Fixed non-original SWs falling back to default EVA messages
Ok, sight lines seems to be fixed, but looks funny, like shadow of some castle, bricks....
And debris with long characters in list seems to work, I put this on tank:
DebrisAnim=Dbris3sm,Dbris4lg,Dbris4sm,Dbris6sm,Dbris7lg,Dbris7sm,Dbris8sm, Dbris9lg,Dbris10lg,Dbris10sm,Dbris3sm,Dbris4lg,Dbris4sm,Dbris6sm,Dbris7lg, Dbris7sm,Dbris8sm,Dbris9lg,Dbris10lg,Dbris10sm,Dbris3sm,Dbris4lg,Dbris4sm, Dbris6sm,Dbris7lg,Dbris7sm,Dbris8sm,Dbris9lg,Dbris10lg,Dbris10sm
MinDebris=5
MaxDebris=6
As you can see, in both case when GIs destroyed tank, those debrises are spawning which means that tag seems working.
edit AlexB: Broke the long line down. _________________
I opened rulesmd.ini and typed search for DebrisAnim= and I stopped counting when I got 100 of those, and the half list of such. So tons of Techno types are using DebrisAnim= instead of DebrisAnims=
I even saw about 30 typos of Maxdebris= instead of MaxDebris= _________________
It is indeed 'DebrisAnims', look it up yourself at address: 00444368
To prevent any further confusion or discussion, it is 'MaxDebris': 0044439C _________________
Ah I got it why it worked for me. Its because of Min/MaxDebris settings, so if DebrisAnims was misspelled, game put debrises on default list perhaps.
I fixed typo, put on 20 debris, destroyed that Titan, and seems that it works with longer list, I notice different debrises
Nevermind, any new test guys? Or again, nobody interested... I told you that you cannot depend on me and my testings only, if I report something that works, you should test out your own combinations too. This was perfect example, I am not familiar with debris thing, I am not interested or using them, I just tested it using Westwood's misspelled code names. Luckily we had Apollo and RP to correct me. _________________
If AttachCloakWH is used as regular warhead for a regular weapon, only the vehicles in the area where the weapon was fired will be affected (cloaked).
But if fired by the SW, it will give invisibilty not only to vehicles, but will Attach the specified animation and will cloak the infantry and the buildings in the area, too, even if the warhead is set to 0% for their armor and should ignore them. QUICK_EDIT
Can you concretize this a bit, maybe with rough version numbers? Was it working in October, but not working since November? Or was it more like broken in 0.5? _________________ QUICK_EDIT
I was looking through the posts here to check off the confirmed blueprints and bug fixes, but I noticed only about a third of them were confirmed yet. I see several feature requests, also some bug reports, but very often the stuff isn't confirmed working or fixed later. I haven't looked at all the items yet to see whether there are posts on them, but it doesn't look good. This surprised me, because I thought several more issues have been tested already and only a few have not.
Mention what works and what not, but please, do not mention such things to me in chat. I cannot keep track of the chat or quote the chat, and also I have to either handle the report immediately or weed through dozens of places to collect the reports. I'm not gonna do that, for obvious reasons. It is already difficult to find out what was tested here completely, not only partially. I know this part of the work isn't fun; I know because I've been the one creating the bug reports and blueprints on LaunchPad for people who only mention issues here or in chat instead of where they belong -- and I don't want to continue like this.
This was the biggest Ares version for quite some time, maybe not measured in new features, but definitely in terms of changed lines of code. It has already been delayed for about a month, and I think everybody sees that it will miss even that deadline. Also, I still have lots of work in front of me, with some issues still left to be resolved, and finally I'll still have to write the documentation for all these changes. AI SW Targeting alone could be half a novel.
Another point is that whenever I'm about to call it a day, new issues come up that have their roots in the past and should have arisen and been resolved weeks ago already. So, when I'm mentally on the home stretch for the release, I have to stop and go back and revisit some older feature. You have no idea how demotivating this is. This led to my batteries being almost depleted, and the release date as a station to charge them is still kilometers away.
At the moment I'm also a little thin-skinned because of a recent incident which prevents me from working with full power. The batteries now also leak at the moment. _________________ QUICK_EDIT
- Ares' new warhead effects appear to be applied at the location of the projectile's hit
- MessageDelay is now properly applied to SW and building event-related text messages
- Crush command works again
- Message.SilosNeeded works and displays at roughly the same moment the EVA report is played
- campaign list extensions work as shown in the picture posted earlier
- KillDriver.Owner works, I could change between Special and Civilian for Morales' warhead. In a SP mission, even though I wasn't allied to Civilian, Morales stopped firing at the unit when the targeted tank was emptied. This is still something that mission designer should check whenever he modifies alliances of JP or Neutral
- PoweredUnit handling no longer only looks at the first building but all of them
- Factory Owners remaining active when objects like ConYard are undeployed and deployed again seems to work
Shroud:
- while the recent shroud changes are good, I'll note this thing. I'm not sure why this area is being revealed, especially considering it's at height 8 compared to the GIs while for a difference in height of 4 it seems fine
// EDIT: Original game bug
- the issue which prevented a SW.AutoFire=yes, SW.Targeting=Self Force Shield from firing at its own provider building with ForceShield.Modifier=0% is fixed
- multiple SuperWeapons on one building work but it seems if a SW with SW.RangeMaximum is listed under SuperWeapons instead of the original SuperWeapon, it will not be possible to fire it
- SW.RequiredHouses and SW.ForbiddenHouses work
- SW.AuxBuildings and SW.NegBuildings work
- Inhibitors work on buildings and units, even the ones that move, wow!
- SW.Warhead=<none> thing on Genetic Mutator and Nuke doesn't crash the game
- Chronosphere clone's SW.Animation (the animation which is the looped portal at the source location for the original SW) only displays the very first frame for a brief second and then you have to remember where you opened the portal cause the animation isn't visible anymore; the issue seems to go back all the way to 0.4 at least. Shamefur dispray, testers.
MultiEngineer:
- There is definitely something wrong with the logic. Even though in skirmish of Mental Omega MultiEngineer is set to be always in play, there are matches in which it is possible to capture a building with a single Engineer just as if the ME settings were not "parsed" at all for the match. In the second match right after ME failed in the previous one, it worked properly again. _________________ mentalomega.com QUICK_EDIT
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Sun Jan 25, 2015 8:07 pm Post subject:
Speeder wrote:
- Chronosphere clone's SW.Animation (the animation which is the looped portal at the source location for the original SW) only displays the very first frame for a brief second and then you have to remember where you opened the portal cause the animation isn't visible anymore; the issue seems to go back all the way to 0.4 at least. Shamefur dispray, testers.
It never worked with clones actually. I found it out around 0.3, but since even that was after Alex explicitly said he had enough of fiddling with that, I just shrugged. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
That cannot be right. I still have two Chronospheres in my rules, still back from testing this, and they both show the default ChronoPlacement animation. I changed one to WARPOUT, and it played to end. I remember I looked into this issue back then (I was suspecting AutoFire), so it's not like I didn't care.
Looking back, recoding the chronosphere with support for moving buildings was a too big undertaking for me, with just about three months of experience working on Ares. And if I could, I would remove that part of Super Weapons, as I still cannot recommend this feature. _________________ QUICK_EDIT
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Mon Jan 26, 2015 10:24 pm Post subject:
I had an 1x1 Chronosphere for a long time and I never seen the source loopanim (bubble warpanims worked at both), even if I utilized all tags or none.
Ultimately I cut it out instead of reporting - Mev said it would be too confusing with such a setup. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
New binary, with some more fixes. While there are still some issues (not as many as a few days ago) to be confirmed, I prepared to start writing the documentation. This will keep me busy for a few days of boredom. Use this build for now, as it should almost be the RC. Maybe I'll deliver a proper RC soon; that really depends on the number of new bugs that come up in the next days.
Sight should now work as in 0.8
Apply Verses for AttachEffects even if the warhead has no owner (GenericWarhead, ...)
Support SuperWeapons= on SW.AITargeting=Self, and launch site search
GenericWarhead now checks ranges and power requirements on firing building
The way the Nuke Silo is picked is changed to support power and range checks
Fix for the Chrono Placement animation issue on Type=ChronoWarp SWs
When writing the documentation, I found some more bugs that I couldn't leave unfixed. I shouldn't start writing the documentation... I also removed the Reveal.FullMap tag, because it was inconsistent. No new tag is required, just set SW.Range=-1 instead, just as you would on the Sonar Pulse. And Ares got a bit smaller again: close to 900kB now.
SecretLab.GenerateOnCapture did not work. It shouldn't ever have worked like that. false alarm
Full-map Sonar Pulse was broken and still showed the target cursor
Infantry ejected from OpenTopped vehicles by KillDriver are fixed
Infantry that KillDriver can't eject are registered as destroyed (which might fix some map triggers not firing)
_________________ Last edited by AlexB on Fri Jan 30, 2015 2:07 pm; edited 1 time in total QUICK_EDIT
Joined: 22 Nov 2010 Location: Iszkaszentgyorgy, Hungary
Posted: Fri Jan 30, 2015 11:26 am Post subject:
Impossible, I used GenerateOnCapture for YEARS now, it never failed me. _________________ "If you didn't get angry and mad and frustrated, that means you don't care about the end result, and are doing something wrong." - Greg Kroah-Hartman
=======================
Past C&C projects: Attacque Supérior (2010-2019); Valiant Shades (2019-2021)
=======================
WeiDU mods: Random Graion Tweaks | Graion's Soundsets
Maintainance: Extra Expanded Enhanced Encounters! | BGEESpawn
Contributions: EE Fixpack | Enhanced Edition Trilogy | DSotSC (Trilogy) | UB_IWD | SotSC & a lot more... QUICK_EDIT
Kinda late, I'll make it short. I just uploaded a new binary which fixes the HunterSeeker and EnemyBase targeting types, and it also removed the SecretLab fix that was not needed. This version is the Release Candidate for Ares 0.9. On LaunchPad there's a package containing a preliminary documentation. All features are described, but it's still rough around the edges, and there are some errors to fix.
The RC phase should not take too long, and I planned to have 0.9 out no later than mid-February. _________________ QUICK_EDIT
thats work fine.
A little complicated for understand correctly, but now i have completly understand how the AI targeting work.
Thanks Alex for the explication. QUICK_EDIT
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum