Welcome to Steelbeasts.com

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Retro

Members
  • Content count

    1,605
  • Joined

  • Last visited

About Retro

  • Rank
    Senior Member

Personal Information

  • Location
    Austria
  • Interests
    Take a wild guess
  • Occupation
    Typist

Recent Profile Visitors

2,357 profile views
  1. I think I once had that with my anti-virus program causing it..
  2. Uncanny valley for landscape perhaps?
  3. I am wondering if this should be a feature of the 'camouflage' selection of a specific party (so something that's an intrinsic feature rather than an explicit setting). Or mabye a combination of 'camouflage' and 'mission date' (so, just to throw out some ideas, a 1970s 'US camo' unit would not have individual radios, while one featured in '2010' scenario would have it..)
  4. Oh wow.. that page says volcano man won two primetime emmys..
  5. (I guess you suspected this already) - nope.
  6. Hmm I guess the game quickly moves you out of the TC spot, then back in again.. resetting the CITV to default values in the process..
  7. Hm, just how many of these lines did you add before you began encountering problems?
  8. Are forest fires not a huge problem when doing live-firing exercises in these environments? Or do they happen anyway (or maybe not at all and it just looks quite dry to me)?
  9. Everytime someone contributes something to this topic my heart skips a beat..
  10. Seems the heightmap that is missing is called Nam2-625.hgt (which is not part of our normal distribution). It might be a renamed 'Nam2.hgt' (which IS being shipped by us) but that's just a guess..
  11. Thanks for the report
  12. The problem is that there are a number of multi-vehicle units composed of vehicles that are not supposed to be in multi-vehicle units, which the scenario loading code cannot handle (yet). In the scenario in the first post this would be a unit composed of a VW Passat, a Toyota and two UAZ trucks (and possibly others since the loading was aborted after encountering the first such unit). So the (annoying, I know) short-term fix (until the next update comes around) would be to go back to 3.028 and either split up these units into single-vehicle formations or change their type. 'Dangerous' unit types where this problem will manifest itself are all civilian vehicles (cars, trucks, motorbikes - you might remember that back then you were only allowed to create single-unit formations (but with the 'set unit type' it was possible to circumvent that)) and ambulance vehicles - basically everything where the 'maximum formation size' (in the 'new unit' dialog in the mission editor) was set to 1. I'm pretty sure this is a vehicle-only problem.
  13. I thought it was supposed to work that way hmm
  14. Thanks that one should be fixed. It indeed only happens with scenarios created in 4.00x
  15. Yes it is. Please don't use these items (61/62/63)