Jump to content


  • Content count

  • Joined

  • Last visited

About Retro

  • Rank
    Senior Member

Personal Information

  • Location
  • Interests
    Take a wild guess
  • Occupation

Recent Profile Visitors

3,686 profile views
  1. Hummer M2HB MG mounts damaged on game launch

    So hopefully that one's fixed.
  2. Hummer M2HB MG mounts damaged on game launch

    thanks! :beer:
  3. Hummer M2HB MG mounts damaged on game launch

    Thanks! I have to sound greedy/annoying (plus I was not exact in my request), but I'd like a sce with a single HMMWV and nothing else..
  4. Hummer M2HB MG mounts damaged on game launch

    I wonder if you could create a SB1 scenario featuring just the Hummer..
  5. Leo 1 Azimuth Indicator

    Try it with stabilization disabled, should work then..
  6. Hosting - display of incompatible version warning

    Hmmm no it is as you said.. the client shoud display its current version (which would be different from the host's). HOWEVER, I think we do not include the 'hotfix' version numbers (ie if the host has (eg) 'V4.023' and the client has 'V4.023 0001' then the game would pick up that there are different versions present, and the client's name would blink, but it would in the UI truncate the version to 'V4.023'..)
  7. Leopard 2E / 2A6

    ballistics-as-a-service, with the full power of the cloud behind it
  8. Ulan FCS question

    I'll have to recheck with the operators but IIRC the Ulan has a 'locked lead' implementation, which means you need to hold down the combined lase/lead button, track the target for a while (>1s), then release the button (at which point the laser fires, if it's enabled), then the lead is 'locked in', the gun sviewels to apply lead/se, the sight mirror counteracts (so that the sight picture actually remains on target - this little 'back and forth' motion could be better simulated in SB I guess), and the gunner is free to fire (without the need to have the lase/lead button pressed).
  9. Error code 3

    Sorry the AAR seems to be corrupt. I'll investigate a bit further and see if it can be salvaged..
  10. I'm not an ulan master by a long shot, but IIRC, as long as the fire control computer is turned on and undamaged you simply use the 'zero' aiming mark.. lay in on target, and fire (in this case the FCS will adjust the head mirror so that whatever way the range was entered the aiming mark will indicate the hit spot [at the correct range]). However, if you turn OFF The ballistic computer, at least on the GNRs side, you should hear a little 'clunk' sound which shows the FCS disconnecting from the head mirror, which (should) go into its default position.. FROM THIS POINT ON the etched superelevations on the sight should be used (if you look through the TIS is should actually also display a changed reticle, called NOTFS)
  11. ULAN systems

    These entries are all either fake or read only (at least in the non-classroom version). Clicking +/- does nothing, JUST does nothing If you cycle until you get to the GRAUSWAHL item (which means 'device selection'), you can press the EING ('ENTER') button to enter into a little submenu, which lets you turn certain subsystems on/off (you can cycle through these subsystems by clicking the toggle switch again) by pressing EING again. I think the only subsystem that you can turn off is the laser. If you cycle all values until you are at the GRAUSWAHL item again, you can leave the menu by pressing the EING button again That's it, AFAIK
  12. Ulan bugs

    Knock out the AI GNR and see if it works then.. thing is, our AI gunner most likely switches these values immediately back to values he can work with, so you dont' see any change as the TC
  13. Error code 3

    That's not related to the actual error.. is there anything else? Could you upload the AAR?
  14. Wind correction not working on CV90-35 DK-NL

    Can you please give any more information what's not working? IIRC on the -DK variant met properties cannot even be entered, an in the -NL it is only the TC who can change these settings via the MFP..