Jump to content

Toggle this categoryToggle Message Visibility   Welcome to our Community, Guest!

Get involved and become a part of our growing community. It's absolutely free! Register an account and join us today. Already a member? Sign in!

- - - - -

List of Known Issues for Level Designers


2 replies to this topic

#1 AndY

    Evil Bunny

  • Coordinators
  • PipPipPipPipPipPipPip
  • 889 posts

Posted 07 October 2010 - 09:59 AM

The following is a list of Known Issues that could cause problems in custom levels. We are working to resolve them as quickly as possible, but if you would like one of these items fixed before the others (to be used in a custom map), you can let us know by contacting us at the following address: support@overwatchmod.com


  • Placing vehicles in a map may cause a crash when loaded on a dedicated server
    Problem: Entities for four-wheeled vehicles placed in a level may cause a crash when loaded on a dedicated server.
    Status: Being fixed.
    Recommendations: This issue should be resolved soon. In the meantime, we don't recommend adding any vehicles to your map.

  • Parenting func_brush_ow entities may cause crash on round reset
    Problem: A func_brush_ow entity that is parented to an object that has the ability to move has the possibility of causing a crash whenever the round resets.
    Status: Pending.
    Recommendations: Avoid parenting func_brush_ow entities where possible. Though if or if not the game will crash on a particular setup of a parented func_brush_ow is consistent, so if you have a compile that does not experience the crash, that compile is not likely to ever crash due to the issue.

  • No info_player_gm_ow in a level will cause a crash when a player attempts to join OW
    Problem: If no info_player_gm_ow is present in a level and someone goes to join the OW team, the game will crash.
    Status: Pending.
    Recommendations: Place an info_player_gm_ow entity in your map.

  • Physics props may cause a crash if they are inside a solid brush entity
    Problem: Any prop_physics[_multiplayer[_ow]] entity may cause a crash if it is inside a brush entity that can be made solid, and a player walks near the props.
    Status: Under investigation.
    Recommendations: We recommend using prop_dynamic entities in those situtations until this issue is resolved.

  • Entities env_indicator_ow and env_hint_ow may cause a crash if no icon is defined RESOLVED
    Problem: The env_indicator_ow and env_hint_ow entities may cause a crash if the GmTexture, RebelTexture or TipTexture key values are empty.
    Status: Fixed in 1.3.5.
    Recommendations: Set a path to an icon *.vmt file in the GmTexture, RebelTexture and TipTexture keys of entities env_indicator_ow and env_hint_ow.


  • Dynamic node links stop working after a round reset and may cause a crash RESOLVED
    Problem: Entity info_node_link may cause problems and/or crash if placed in a level.
    Status: Fixed in 1.3.0.
    Recommendations: We don't recommend adding any info_node_link entities to your map until this issue is resolved.


  • Barnacles picking up a Rollermine may cause a crash
    Problem: Barnacles picking up a Rollermine may cause a crash.
    Status: Pending.
    Recommendations: We don't recommend adding both npc_barnacle and npc_rollermine to the same map until this issue is resolved.

  • A GM placed inside the world may cause various issues
    Problem: A few problems may arise if the GM's spawn is placed inside the world.
    Status: Cannot be fixed.
    Recommendations: Please follow this guide to properly place the GM's spawn outside the world, resolving all known issues.

  • Water is rendered black to the GM
    Problem: In-game water is rendered as completely black to the GM.
    Status: Pending.
    Recommendations: Water can be used, it just won't be visible until this issue is resolved.

  • Human NPCs have no animations
    Problem: Human NPCs (like the various rebels and civilians seen in HL2) have no animations when placed in a level.
    Status: Under investigation.
    Recommendations: We don't recommend adding any scripted human NPCs to your map.

  • Metropolice can not use Shotguns properly
    Problem: Metropolice units have various issues when equipped with a Shotgun.
    Status: Under investigation.
    Recommendations: We don't recommend equipping a Metropolice with a Shotgun until this issue is resolved. These weapons can be used: Stun Stick, Pistol, SMG1.

  • Mounted guns (func_tank) are bugged when used by players
    Problem: Mounted guns (as seen in HL2) are glitchy when used by players.
    Status: Under investigation.
    Recommendations: We don't recommend adding a mounted gun to your map until this issue is resolved.

  • Entities move_rope and keyframe_rope don't get rendered properly after a round reset
    Problem: Ropes may appear to get stuck when used (i.e. combine rappel animation).
    Status: Under investigation.
    Recommendations: These can be safely used.



REVISION HISTORY

[ 09 JUN 2012 ] Entities env_indicator_ow and env_hint_ow crash resolved. Crashes due to no GM start and func_brush_ow entities.
[ 19 NOV 2010 ] Dynamic node links crash resolved. Possible crash caused by entities env_indicator_ow and env_hint_ow.
[ 07 OCT 2010 ] Added props-related crash.


#2 AndY

    Evil Bunny

  • Coordinators
  • PipPipPipPipPipPipPip
  • 889 posts

Posted 19 November 2010 - 10:19 PM

Resolved: Dynamic node links crash (Fixed in 1.3.0).
New: Possible crash caused by entities env_indicator_ow and env_hint_ow (Affects 1.3.0+).

#3 AndY

    Evil Bunny

  • Coordinators
  • PipPipPipPipPipPipPip
  • 889 posts

Posted 20 November 2010 - 01:28 AM

Correction: The entity crash affects both env_indicator_ow and env_hint_ow.





3 user(s) are reading this topic

0 members, 3 guests, 0 anonymous users