Jump to content
Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble
Slate Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate Marble

The Loot

Members
  • Content Count

    721
  • Joined

  • Last visited

Community Reputation

3 Neutral

4 Followers

About The Loot

  • Rank
    Battalion Chief

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Easily done by added a wait pushaction to the vehicle between hiding it at the spawnpoint and then unhiding it and making it move. I'd be surprised it that hadn't been implemented already.
  2. You also have to have the tiller check command run at startup of the map.
  3. From what I remember, this sounds like you've exceeded the limit of how many equipment group commands a person prototype can have. You'll either have to remove some commands, or change some of the equipment commands and comment out the "SetGroupID(CGROUP_GETEQUIPMENT);" line. This will make them show up on the main command list, but be aware of the command limit on that, as well.
  4. Perhaps checking for a vehicle colliding with the VO before changing them to barriers, with a short delay and repeat if there's a vehicle there? If you hadn't already thought of that.
  5. itchboy recently figured out a pretty simple fix to make patrolling vehicles respect traffic lights, which is what always caused them to get stuck.
  6. LAFireStation contains the station Alarm command.
  7. I found that the simplest way to do it was to make dummy commands and assign them to any applicable vehicle, which the equipment script would then check for. object FlagHasBarricade : CommandScript { FlagHasBarricade() { SetGroupID(20); } bool CheckGroupVisibility(GameObject *Caller) { return false; } bool CheckPossible(GameObject *Caller) { return false; } bool CheckTarget(GameObject *Caller, Actor *Target, int childID) { return false; } void PushActions(GameObject *Caller, Actor *Target, int childID) { } }; And then in the script CheckTarget section, just add this: if (!Target->HasCommand("FlagHasBarricade")) return false; It makes it very simple to add new vehicles later: just add the dummy command and they're all set.
  8. Alright, finally got it working. The caller creates a copy of themselves at the command position, it gets hidden (normal method caused an issue with getting a final vector, changing model to an invisible one works), find it with another caller command, make it execute the final command at its position, and then delete itself. I was going to just use an empty object prototype, but the prototype of the caller is essential to the functioning of the scripts.
  9. I suppose it's the method that complicates using a vector in this case, but I've seen them used in seemingly similar ways elsewhere. That mod seems to have some gameplay elements I've gone for myself, so I'll probably check it out in general now.
  10. Basically, I'm trying to add a delay when I use a modified LA Call Vehicle Command, so that there's a wait period during the radio audio, and a vehicle behind chosen and taking actions itself. Vector CmdPos = Game::GetCommandPos(); is outside of Child sections at the top of the script. Under ChildID 0, I have tried both of these commands: Caller->PushActionExecuteCommand(ACTION_APPEND, "PcmdCallALSAmb", CmdPos, 1, false); - It throws this error log: Caller->PushActionExecuteCommand(ACTION_APPEND, "PcmdCallALSAmb", CmdPos.Target, 1, false); - Saw something like that in the Move command, but it throws this much smaller error log: ChildID 1 contains the actual bulk of the script. Is this even possible?
  11. As far as I remember, there were no classic vehicles in that submod. New units with new skins, but most were the base LA Mod Models.
  12. Sounds like there's an error in the xml file, thus it can't load anything in it.
  13. Sure. Hopefully this was the latest one. Haven't really touched EM4 in quite a while. Hoppah's Limited Water Supply Script by The Loot.zip
  14. Simplest thing to do that is just copy and move the virtual objects for the vehicle, and then change the ones that are referenced for the vehicle in the script section. Dealing with things like passengers and transports leaving the vehicle, or opening/closing gates are another project, however.
  15. They're also offset to the driver's side of the rear window, and this goes for marked slicktops, too. Newer model vehicles have completely different lighting setups, however, and Youtube sucks for examples.
×
×
  • Create New...