Jump to content

TonyE

Staff Pukes
  • Posts

    4,369
  • Joined

  • Last visited

  • Days Won

    126

TonyE last won the day on September 19

TonyE had the most liked content!

3 Followers

About TonyE

  • Birthday 01/19/1978

Contact Methods

  • AIM
    eisc0013
  • MSN
    sysop@tgp.net
  • Website URL
    https://www.tgp.net
  • ICQ
    51680916
  • Yahoo
    eisc0013

Profile Information

  • Gender
    Male
  • Location
    Minneapolis, MN USA
  • Interests
    Harpoon, Hockey, Running

Recent Profile Visitors

66,783 profile views

TonyE's Achievements

Grand Master

Grand Master (14/14)

  • Very Popular Rare
  • Reacting Well Rare
  • Dedicated Rare
  • First Post Rare
  • Posting Machine Rare

Recent Badges

164

Reputation

  1. Hmm, it looks like the audio is in the replay even though it wasn't in the livestream. and
  2. I started to take a look and live-streamed it very poorly (audio wasn't in an acceptable format for YouTube). No useful debugging results yet though the Red F-35 just launched on me so there is hope.
  3. Here is a bit about eff115 from the ReleaseNotes.txt HCE - 2009.027 ============== - Chg:B106 GE Implementing a new eff115 (Autonomous Sensor Intelligence) that determines when the AI should turn on active sensors and when to prompt the player to do the same. Added a new log type option to the command line for this, emcon_ai . Also added a new command line option to switch back to a fixed version of the old eff115 that will properly notice if a group's radars are already on. The option is -e i.e. c:\games\HCE\Winharp32.exe -e would revert to the fixed old eff115 that is much more apt to turn on radars than the new code. (thanks Lots of People) With the old eff115 the game took the stance that it is better to radiate than get zapped by an unseen foe. The re-write tempered that approach to use additional logic to only start radiating when it seemed likely the foe could detect your unit. The logging of the new eff115 is comprehensive and might be interesting for you to examine. It is the emcon_ai logging flag.
  4. It does raise the question of who needs the game to still run as Windows XP API level compatible...
  5. Video uploaded, Eric's approach can work and I show it in the video, updating HCE to the current beta. It is an unsupported configuration but happens to work with the builds available right now. There are no guarantees on that continuing to work but chances are good that it will.
  6. TonyE

    IRC chat demo

    Slightly more direct link to the web-client https://web.libera.chat/?channel=#harpgamer There isn't much action these days on #harpgamer but if you know when you are going to give it a go, tip us off and I know I'll try to be there.
  7. Hi aviator, can you tell us one specific scenario you are trying to edit and the BattleSet name? Thank you
  8. Concur, the iterative saving is the best tool. Then if your most recent save is bad, if you go back an additional save/game second chances are great you can load it. Sometimes the last save it bad as part of whatever bug you hit. I'll do a bit of a write-up on old eff115 last this weekend. You don't need to do additional logging until problems are more narrowed down. The additional logging is more of an on-demand thing, Y:"Hey Tony, why are my tankers always empty?" M:"Run through it again with the refuel logging turned on and send me the ge.log file." The logs make some sense the more you read them. The refuel once for instance will give you information I think you'd understand without any assistance.
  9. Yes, add some ordnance like the AGM-84 and I'm in
  10. Hmm, modelling the seasonal affect on daylight would be a lot easier than modelling terrain. I'd even welcome day/night changing by longitude before dreaming up too much fun for latitude. If you get bored and stumble upon a source of the equations for day/night/dawn/dusk by date & lat/lon, that is something I could add to the game in a weekend.
  11. Do you happen to recall if the DD remained a localized contact (no uncertainty zone diamond lines)? Fratricide is purposely allowed for AAMs, torpedos have a bit more advanced modelling that are dependent upon the situation (whether still being wire guided to an exactly detected target for instance).
  12. TonyE

    Question...

    There is also the possibility that the transport needed to hang around the drop zone for a specified period of time. Unless the scenario orders were specific about dropping the paratrooper ordnance, sitting on station, or just keeping those aircraft alive, one would have to open up the scenario in the editor and examine the victory conditions.
  13. Tonight I recorded a video showing how to install and use the basics of mIRC and also how to come chat on #harpgamer with a web-based IRC client.
  14. That is fantastic news, thanks Don!
  15. The following rules are part of the function get_default_loadout. You can see what mission is chosen by activating mission logging with the -l mission command line option: Fighter - Natural loadout type is MISSION_ATA (air to air) Attack - Natural loadout types are MISSION_STANDOFF MISSION_SEAD MISSION_GUIDED MISSION_UNGUIDED Bomber - Same natural loadout types as Attack That leads to the question of, so when is get_default_loadout called and why? 1. Upon scenario load (File\Load User Scenario, ...) if the loadout defined in the Scenario Editor (SE) is invalid. This can happen if loadouts are re-assigned in the database. So it is possible here for a perfectly good loadout to get unloaded and changed. 2. When creating the initial air patrols for the AI or if the Player has chose auto formation air patrols. Note that this is only for ships (but not aircraft carriers) and mobile land units. So it is possible here for a perfectly good loadout to get unloaded and changed. 3. When a saved game is restored and the loadout index is no longer valid the game tries a couple of ways to divine what was meant. If that divination fails, the default loadout is requested. You can see some indications of this by activating AC AI logging with the -l ac_ai command line option. The loadout name to MISSION type mapping was last changed in 2008 and is the following. The number MISSION_FERRY = 000 can be matched up with the loadout type in the Platform Editor (PE). Holler with more questions. // ALE 20081030 Updated loadout type distribution // MISSION_MAP maps misison IDs into MISSION_TYPES MISSION_TYPE MISSION_MAP[/* mission */] = { MISSION_FERRY, // 000 "Cargo" MISSION_ASSAULT, // 001 "Assault" MISSION_TANKER, // 002 "Tanker" MISSION_PATROL, // 003 "Patrol" MISSION_NUCLEAR, // 004 "Nuclear" MISSION_STANDOFF, // 005 "ASuW" MISSION_STANDOFF, // 006 "ASuW-LR" MISSION_SEAD, // 007 "Sead" MISSION_SEAD, // 008 "Sead-LR" MISSION_GUIDED, // 009 "Precis" MISSION_GUIDED, // 010 "Precis-LR" MISSION_UNGUIDED, // 011 "GP" MISSION_UNGUIDED, // 012 "GP-LR" MISSION_ANTIRUN, // 013 "Anti-run" MISSION_UNGUIDED, // 014 "BAI" MISSION_ATA, // 015 "Intercept" MISSION_ATA, // 016 "Escort" MISSION_ASW, // 017 "ASW" MISSION_ASW, // 018 "ASW-LR" MISSION_AARMR, // 019 "AAmr" MISSION_UNGUIDED, // 020 "CAS" MISSION_AARMR, // 021 "AArm-LR" MISSION_DECOY, // 022 "Decoy" MISSION_DECOY, // 023 "Decoy-LR" MISSION_FERRY, // 024 "Ferry" MISSION_FERRY, // 025 "Patrol-2" MISSION_UNGUIDED, // 026 "GP-2" MISSION_ATA, // 027 "Intercept-2" MISSION_GUIDED, // 028 "Precis-2" MISSION_NUCLEAR, // 029 "SIOP-2" MISSION_ATA, // 030 MISSION_ATA, // 031 MISSION_ATA, // 032 MISSION_ATA, // 033 MISSION_STANDOFF, // 034 MISSION_STANDOFF, // 035 MISSION_STANDOFF, // 036 MISSION_STANDOFF, // 037 MISSION_STANDOFF, // 038 MISSION_STANDOFF, // 039 MISSION_STANDOFF, // 040 MISSION_STANDOFF, // 041 MISSION_STANDOFF, // 042 MISSION_STANDOFF, // 043 MISSION_SEAD, // 044 MISSION_SEAD, // 045 MISSION_SEAD, // 046 MISSION_SEAD, // 047 MISSION_ANTIRUN, // 048 MISSION_ANTIRUN, // 049 MISSION_ANTIRUN, // 050 MISSION_GUIDED, // 051 MISSION_GUIDED, // 052 MISSION_GUIDED, // 053 MISSION_GUIDED, // 054 MISSION_GUIDED, // 055 MISSION_GUIDED, // 056 MISSION_GUIDED, // 057 MISSION_GUIDED, // 058 MISSION_GUIDED, // 059 MISSION_GUIDED, // 060 MISSION_GUIDED, // 061 MISSION_GUIDED, // 062 MISSION_GUIDED, // 063 MISSION_GUIDED, // 064 MISSION_GUIDED, // 065 MISSION_GUIDED, // 066 MISSION_GUIDED, // 067 MISSION_GUIDED, // 068 MISSION_GUIDED, // 069 MISSION_GUIDED, // 070 MISSION_GUIDED, // 071 MISSION_ASW, // 072 MISSION_ASW, // 073 MISSION_ASSAULT, // 074 MISSION_ASSAULT, // 075 MISSION_ASSAULT, // 076 MISSION_FERRY, // 077 MISSION_ASSAULT, // 078 MISSION_ASSAULT, // 079 MISSION_UNGUIDED, // 080 MISSION_UNGUIDED, // 081 MISSION_UNGUIDED, // 082 MISSION_UNGUIDED, // 083 MISSION_UNGUIDED, // 084 MISSION_UNGUIDED, // 085 MISSION_UNGUIDED, // 086 MISSION_UNGUIDED, // 087 MISSION_UNGUIDED, // 088 MISSION_UNGUIDED, // 089 MISSION_UNGUIDED, // 090 MISSION_UNGUIDED, // 091 MISSION_UNGUIDED, // 092 MISSION_UNGUIDED, // 093 MISSION_UNGUIDED, // 094 MISSION_UNGUIDED, // 095 MISSION_UNGUIDED, // 096 MISSION_UNGUIDED, // 097 MISSION_UNGUIDED, // 098 MISSION_ATA, // 099 MISSION_ATA, // 100 MISSION_ATA, // 101 MISSION_ATA, // 102 MISSION_ATA, // 103 MISSION_DECOY, // 104 MISSION_TANKER, // 105 MISSION_TANKER, // 106 MISSION_TANKER, // 107 MISSION_AARMR, // 108 MISSION_AARMR, // 109 MISSION_DECOY, // 110 MISSION_DECOY, // 111 MISSION_DECOY, // 112 MISSION_PATROL, // 113 MISSION_PATROL, // 114 MISSION_PATROL, // 115 MISSION_NUCLEAR, // 116 MISSION_NUCLEAR, // 117 MISSION_NUCLEAR, // 118 MISSION_NUCLEAR, // 119 MISSION_ASW, // 120 MISSION_ASW, // 121 MISSION_ASW, // 122 MISSION_ASW, // 123 MISSION_ASW, // 124 MISSION_ASW, // 125 MISSION_ASW, // 126 MISSION_ASW, // 127 };
×
×
  • Create New...