Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by galinette

  1. I don't understand, if you set 10 waypoints in ME you have them loaded right? The only thing that's not implemented in ME is BAD, you need to enter them in the cockpit. But BADs are much more easy to type in than full coordinates.
  2. Is this possible with other Aircraft? You can't use BAD function on the INS for this?
  3. Hi, The other day, on a busy server, I had these values. (Sorry for the low res, VR screenshots can't be better) What does these mean?
  4. Hi, I'm adding a F10 menu item through missionCommands.addCommandForCoalition Is there any way to retrieve the group or client which triggered the menu item in the called function? Thanks!
  5. When I have a radar+magic lock (triangle around target), the IFF "A" doesn't appear on the HUD. Is this a bug or a real behavior of the mirage? This makes identification after a merge super tricky in some situations, and you often can't fire your fox2 without a heavy risk of killing the wrong target.
  6. I have tried setting the UHF ARC-159 Function Inc/Dec binds on an encoder. It doesn't work : one bind does nothing, the other one toggles between OFF and BOTH The UHF ARC-159 Mode Inc/Dec binds (Preset/Manual/Guard), on the other hand, work as it should.
  7. The Mirage is definitely way behind against fox3 aircraft. However, it's super challenging and rewarding. You have to rely on discretion (radar off, low level terrain flying in the mountains), observation (contrail spotting, RWR, AWACS messages) to sneak below ennemy aircraft, fast climb and shoot your missiles from behind/below. And leave the place quickly before another patrol spots you. You won't have a very good kill/death ratio, but that's way more fun than firing fox3 from 40nm.
  8. I can confirm the bug is still there. I can relight after a manual in-flight engine stop, or after a high altitude flameout, but not after inverted flight.
  9. Hi, I have a i7 6800K. The multiplier for 3-6 active cores is 40x and for 1-2 active cores is 44x. Base frequency is 100MHz. Now, when running DCS or another single thread app, the reported active core count is 1 and sometimes 2, never more. However, the "Max Core Frequency" reported by XTU is 4.00GHz, not 4.40GHz. Do you know what could be the cause? Thanks!
  10. You can bind them, but it requires a small hack to the mod. The file is attached (open for instructions). This gives an axis for the UHF/VHF channels, and binds for VHF keys. At each DCS update, the default.lua file will be overwritten, you need to insert the three lines again. galinette-m2k.lua
  11. I can confirm the FPM now moves diagonally with rudder input at 90° bank angle, instead of laterally. The bug is still there.
  12. I can confirm this works now in the OB. Only the mouse wheel support was removed, which is somewhat disappointing, but at least the offset is now usable.
  13. I wanted to try VR cockpit clicking with my Virpil grip thumbstick & thumbwheel. In DCS, you can set joystick binds for left/right mouse buttons, and wheel up/down. But you can't use the ministick axis for moving the mouse. So I made a small autohotkeys script for moving the mouse cursor with two axis. Now the analog thumbstick moves the mouse, while clicking on it is left mouse button. The wheel acts as the mouse wheel, and clicking on wheel is right mouse button. This gives full mouse control with the grip hand thumb. I don't know if I will keep t
  14. I've played with the excellent DCS Menu Nav autohotkey script, but it wasn't fulfilling perfectly what I needed: - Sounds somewhat intrusive - The OSD wasn't visible in VR so I had to rely on sound only - The menu doesn't contain all the F keys so the OSD can't be placed properly in all cases I did some heavy modifications/tests and ended up with a very simple script which just moves the actual mouse cursor to one of the 12 menu entries, cycles through it, and allows mouse click. So now, I have a clickable encoder, which places the mouse over the menu entries, and cl
  15. No, the alignment is wrong in FS2020 which has direct WMR support. What I believe, is that other environment make you look at infinity less often, and some divergence strain is compensated by looking to closer objects. In flight sims, you are most of the time looking at infinity for long periods, and slight image divergence causes high strain. This is well known in the stereo/VR industry, having objects at infinity is avoided whenever possible as it's super incomfortable with not perfectly aligned hardware.
  16. Now I'm very happy with my custom DCS aligment, I can play 3 hours without significant eye strain. I just tested with FS2020... after 15 min it was hurting due to divergence. So it does not seem a DCS issue. But G2s seem to be calibrated like ass.
  17. I have found an interesting workaround, I put my binds in a separate file. Then, in default.lua, I only have to add three lines which will include the other file. My separate file is not overwritten during updates, just the include lines, which I keep commented in the separate file. Attached, an example for M2000-C and F14B galinette-f14bp.luagalinette-m2k.lua
  18. Followup on my DIY alignment bench (I have improved it a bit, by letting the headset still, while translating the camera, on my glass desk, with some teflon pads for easy slide, and some wood blocks with strong double sided stops for the 67mm stop). The slight horizontal residual misalignment was, as the picture shows, about 75% of the diameter of the mirage 2000 FPM circle, in divergence. Divergence is quite bad, so I shifted slightly in/out symmetrically for right and left eyes, until I get repeatable results. We will see if I get less eye strain like this.
  19. HSI offset knob changes rho by 15nm steps (instead of 0.1nm) and theta by something like 6° Also, when changing one of those parameters (theta or rho) by some amount, then going to the other parameter, and changing it by a single step, the values jumps by a large amount. As if both values were changed at the same time when turning the knob, but updated on the HSI when changing it by one step. TRK attached hsi-bug.trk
  20. Hi Razbam, Now, the HSI knob works both directions. But, it changes rho by 15nm steps (instead of 0.1nm...) and theta by somthing like 6° And, that's not the worst : when changing one of those parameters (theta or rho) by some amount, then going to the other parameter, and changing it by a single step, the values jumps out like crazy. As if both values were changed at the same time when turning the knob, but updated on the HSI when changing it by one step. In short: Before last update : HSI offset was usable, but if you needed to decrease rho or theta, you had
  21. Ryzen are good for gaming but are much behind Intel when it comes to single thread performance. I would expect DCS performance to be much lower. I'm pretty sure the chipset for 9900K and 10900K is totally different from a 6800K which is 3-4 generations behind.
  22. galinette

    RWR update

    Same for any mod customization (such as new binds, etc...). Use OVGME to add/remove your customizations:: https://wiki.hoggitworld.com/view/OVGME
  23. You could dim the lightmaps. This would not solve the difference between 0 and first crank being too large, but still allow for lower brightness. The brightest setting being useless anyway.
  24. It has a bind, "Engines STOP" in "Engine & Fuel". I use it and just checked it's there and works. Unfortunately, only in the core folders. DCS stores modified file in a "Backup" folder when overwriting during an update, but you still have to restore it.
  25. 6800K + RTX3090 : I'm now at 80% SS, 1.0 DCS PD, MSAA 2x I need to disable shadows and it's at a nearly rock solid 45fps. With shadows, everything is much nicer, but I have a lot of ~35fps drops. Does this seem what I should expect? Would a newer CPU (10900K) bring a (very) significant improvement, or do you have similar performance? I need 64Gb for work purposes so would be a big $ figure... (MB+CPU+RAM...)
  • Create New...