Jump to content

Isnogud

Members
  • Content Count

    32
  • Joined

  • Last visited

About Isnogud

  • Rank
    Member
  • Birthday 10/30/1970

Personal Information

  • Location
    Berlin
  • Occupation
    it-consultant
  1. Our happy slaughtering will start on Sunday 05/11 approximately at 20:00 GMT. We are really looking forward to meet UK Armour again, even if we get our behinds kicked ... Great guys
  2. wow, now that's skinning quality !!! More this, less other :luxhello:
  3. Uh that's a great idea, why not make use of the already existing speech api, nice thx Lt DeFault Time to plunder and torch Microsofts SDK's again, hooray :luxhello::luxhello::luxhello:
  4. thx Gibsonm, i will implement this patrolled region behavior for some troops or 3rd party bad guys The workaround 'copy to other side and back again' sounds like a quest for a hobbit But actually thats a nice idea and it does'nt take that time at all. Sure, it's the commanders job to tell the driver, wehere to go. But ehm as long as we don't have a voice command feature like in hawx it would be a fine feature. But well, not sooo necessary, i give you that. Ok, taking in mind the driver would drive through roundabouts :bigsmile:... maybe that waypoint thingy was a dumb idea:c:, forget it. But now that i think of voice commands ... wantwantwant :luxhello:
  5. Well the NavMesh used by SteelBeasts in particular is something, i do not fully understand. I mean, how SB uses it. With that explanation from unity3d, it is starting to get clearer **** A navigation mesh (also known as the Navmesh) is a simplified representation of world geometry, which gameplay agents use to navigate the world. Typically an agent has a goal, or a destination, to which it is trying to find a path, and then navigate to that goal along the path. This process is called pathfinding. Note that Navmesh generation (or baking) is done by game developers inside the editor, while the pathfinding is done by agents at runtime based on that Navmesh. In the complex world of games, there can be many agents, dynamic obstacles, and constantly changing accessibility levels for different areas in the world. Agents need to react dynamically to those changes. An agent's pathfinding task can be interrupted by or affected by things like collision avoidance with other characters, changing characteristics of the terrain, physical obstacles (such as closing doors), and an update to the actual destination. http://docs.unity3d.com/Documentation/Manual/NavmeshandPathfinding.html ****
  6. haha, you got it, right :bigsmile::luxhello::bigsmile:
  7. sure, right, the route command would be the current way to do this, absolutly. It's just a thought, rather than to draw lines in the map during battle, it would be great if a setting of "quick waypoints" would be possible, where the driver ai can actually "surprise" me In a way of 'giving the ai some personality' if you know what i mean :bigsmile:
  8. ah, do you mean setting a waypoint with "lase to set waypoint"? What i meant was, oh how do i put this: When i'm commanding a unit, i wish i could go to map view, set a few waypoints, which the driver then steers to (without bumping into trees or stuff:)) Ok nothing too important maybe, but it's the little things ...
  9. To get back to what Azure Lion asked in the beginning: What would you like to see in Steel Beasts? - Scenario Editor: AI patrolled regions (maybe the possibility in the scenario editor to specify a region for specified units with some extra markers to tell them, how long they should stay at the marker) - Scenario Editor: the allmighty copy and paste functionality - InGame: On the fly waypoints. When commanding a unit, it's always very time consuming to steer the vehicle to a designated area. Why not give the possibility to just set some waypoints in the map and let the driver do his work? Ok, thats just a suggestion in generally. - Settings: would it be possible to divide the commands in vehicle sections? This thread is far too interesting that some hate mongers should destroy the purpose of it. So let's ignore the ignorant and care for the caring
  10. Ok, scenario is approved now
  11. Yes, the same problem occurred twice now, as soon as the going gets tough, network synch is getting very shaky...
  12. Ok, i have uploaded the scenario. Name is: "Quo Vadis (3.002)" Should be approved in a few hours http://www.steelbeasts.com/Downloads/p13_sectionid/262 It would be great if you could take a look at this taking in mind, there are massive network synchronization problems now in 3.002 Back in 2.654 it ran very smooth bit now nobody can see the correct position of the other, not in map nor in external view... I don't know, if this problem is pointing to the map, the unit count or whatever.... Well, maybe i should write this scenario new from scratch other than converting old scenarios ...
  13. Version 1.0

    133 downloads

    This one was my first scenario, so be kind ;) Scenario description is in german, now google translator, do your worst ... ;) 1.) LAGE a.) Feind: Fdl Kräfte stossen im benachbarten, westlichen Gefechtsabschnitt schnell Richtung Norden vor. Zweite 104 mit PzGren 112 tritt seit einer Stunde auf Feind an. Im Raum um Pfreimd wurden vor 5 Stunden feindl. Truppenbewegungen gemeldet, vermutlich baut Feind Versorgungslienien für weiteren Angriff auf. b.) Eigene: Wir, die 4.te Kp/PzBtl 104 und Teile PzGrenBtl 112 stehen derzeit im Verfügungraum und stellen Gefechtsbereitschaft her, um im weiteren Vorgehen die Flankensicherung für die 2.te Kp im westl. Gefechtsabschnitt zu sichern und eigene Aufträge zu erfüllen. 2.) AUFTRAG: Wir haben den konkreten Auftrag, die Versorgungslinien der feindl. Truppen im Raum Pfreimd zu unterbrechen. Im Vorgehen auf Pfreimd ist sicherzustellen, dass keine Feindkräfte unsere westl. Abschnittgrenze durchbrechen wodurch die 2.te Kp flankiert werden könnte. Ihr heutiger Auftrag ist erfüllt, wenn Sie Ihre Teile im VVD bei Pfreimd untergezogen haben. Möglicherweise abweichende Aufträge werden Ihrem cO gemeldet. Einzelaufträge: -legt cO fest. 3.) DURCHFÜHRUNG: -legt cO fest. 4.) UNTERSTÜTZUNG a.) ARI: 3 Züge mit je 6 Rohren Anforderung über cO b.) ErsatzFz: 2 Leo2A5; 2 CV90/40-C; b.) Versorgung: 2 x MunLkw; 1 x Wisent; 1 x San; 5.) FÜHRUNG und FM WESEN: legt cO fest Script: Isnogud März 2013 (http://www.sb-target.de/) update : 2013-10-02
  14. Thank you, i will upload the scenario, maybe you guys can find the error(s)
  15. Good morning ok, the message regarding the hotkey file is gone now. I just exported the settings to this std.hkf file under: "C:\Users\username\AppData\Roaming\eSim Games\Steel Beasts\options\std.hkf" so the messages regarding the error can be ignored as well? [10:05:11,056] ERROR: ConfirmDevice failed: D3DCREATE_PUREDEVICE I'm just looking for any cause of problems because yesterday i hosted a scenario that i have written for 2.65 and we had massive problems with network synch between clients. No one could see the real position of the other tank, whether on map nor in F8. Constant network overload even though i was connected via lan. Ok, the scenario is filled with units but still... i just can't figure out, what is different now and what could be wrong with my scenario But ok, i will ignore the debugLog file now. Thx Ssnake :clin:
×
×
  • Create New...