Jump to content

uri_ba

Members
  • Posts

    635
  • Joined

  • Last visited

  • Days Won

    1

Personal Information

  • Flight Simulators
    Current: DCSW, BMS
    Past: LOMAC/FC1/FC2, OF4.5/4.7, FSX/p3d, SSM2007
  • Website
    https://pit.uriba.org

Recent Profile Visitors

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

  1. Hi Everyone a Hotfix for DCS 2.9.1 scripting changes is (finally) released. I'm sorry it took so long. hadn't been touching DCS much lately and it took me a while to validate everything. Happy holydays and happy hunting!
  2. @rel4y IIRC, it's under the initial config button. You'll need to unplug the device after you change it and save
  3. @rel4y Just a small comment. the FLCS emulation feature in my FCC controller does not force the actual forces.. But will use the proportion of the forces where the max value is the one you have stated in the force settings. the force is computed by the gains provided by Arend at the time for the two versions of the hardware he made. "cougar" and "warthog" (very few warthog devices were produced before his passing) for "cougar" 9kg/f was 1.5V (off the 2.5v neutral position). so 1.0v = -9kg/f, 4.0V = +9kg/f in WH it was 2V for 9kg/f, so 0.5V and 4.5V. you can change the controller to WH mode and it might work better with your hardware. and yes, for desktop 4-6 kg force is the limit. I used to fly with 7.5kg in my pit. but I would very much recommend you enable the FLCS emulation. it makes all the difference and allows a much smoother and intuitive flight experience. (less force is required to get a full down deflection) as for jitter in the stick. it's probably just my software, I used samples in intervals which may cause some issues. I recommend you check with another 3rd party software to ensure the jitter is actually there. because from my experience, it was pretty smooth
  4. Hi Everyone. Work on Hound 0.4.0 is progressing nicely it will be ready for initial alpha testing soon (if someone is interested to get a preview build, ping me). But as you patiently wait, we have a new kid on the block the Mudhen. By default Hound provides coordinates in DMS format, the hen is using DMM. To support this in existing hound setup you'll need to add one line in your initialization script. HOUND.DB.useDecMin['F-15ESE'] = true Happy hunting
  5. Great initiative! Just a little tid bit to get your wheels working. If Hound is used in the mission, you can on command (manually or via mission trigger) a hound instance to dump all the contacts it has to a csv file. You can use that file to do what ever you can think of
  6. 0.3.4 is officially out. updated first post
  7. When adding a linked balloon it does not come up in normal staticObject call. The anchor point object also does not have the balloon in getDecs(). Balloon object is present when digging into _G.env.mission.coallition object
  8. In the DCS DB the type name for command center object is `.Command Center` (note leading dot) when calling for example local command = StaticObject.getByName('COMMAND_CENTER') env.info("Height of command center is: " .. command:getDesc()["box"]["y"]) you get back 2023-05-21 06:04:59.778 ERROR GRAPHICSVISTA (Main): Can't open model .Command Center. 2023-05-21 06:04:59.779 ERROR SCRIPTING (Main): Mission script error: [string "test.lua"]:266: attempt to index field 'box' (a nil value)
  9. Hi there! Is there a LUA call/attribute that a server can query a client with to determine if u22 is operating or not? I assume everything is client side, but one can hope I want to know if a pilot has turned on or off his ELINT pod, and to lesser extent in what mode. Maybe something with 'getDrawArgumentValue'? Thanks! Uri
  10. CJS Growler support has been added in 0.3.4. However at the time i'm writing this, 0.3.4 is still in develop branch in github.
  11. I've also installed a dedicated server on my rig. It closes without any CTD alerts. I really can't figure it out, it all worked before.
  12. made a slow repair, then updated to 2.8.3.37854 pagefile is now 32gb. I've removed saved games\DCS and copied just the one mission in after the sim recreated it same CTD without logs with the MT exec. ST seems to be stable however... dcs.log.20230318-MT dcs.log.20230318-ST
  13. dcs.log showed nothing except normal output. I'm trying to compile a test mission, but it's not showing the same behavior (while using the exact same code). I'm currently trying to establish if it's related to assert(loadfile()) which I use extensively in development and not used at all in the mission I was trying to prepare. before the crash I see `WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED` in the dcs.log and that is always the last message
×
×
  • Create New...