Jump to content

legitscoper

Members
  • Posts

    151
  • Joined

  • Last visited

About legitscoper

  • Birthday 05/04/2002

Personal Information

  • Flight Simulators
    SU-25T, AJS37, SU-27
    EF-2000 (soon)
  • Location
    my house
  • Interests
    Programming, Games, Electronics

Recent Profile Visitors

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

  1. Some X56 just break when using Logitech's X56 H.O.T.A.S software. When I tried to set a J-curve, after the change, when I was pulling the stick, values were jumping to max values in 2 places. Same with X axis, but even worse. The same thing can happen when you click calibration button. Here is the fix: 1. Remove the stick from base 2. Unscrew it. You will find a green board 3. Remove white board connector 4. De-solder the hall sensor chip (the one with 8 legs, pretty small, sitting next to magnet mounted on sitck). Remember it's oriention, take a picture, or just match the chip's dot indent with the printed dot on board 5. Connect white board connector, do not assemble the stick base back, not needed 6. Connect the base via USB to PC 7. Run a calibration inside the software. 8. Disconnect the stick 9. Remove the board again 10. Solder back the sensor 11. Assemble everything back. 12. Connect, and voila! It works, at least works for me, and worked 2 times. 13. Do not ever use the software for any curve settings, I use it for RGB only. You might also have a problem of having off-center axes, as it's pretty hard to solder the chip back 100% precise. In this situation you can try to adjust the board position using the 4 screws, and maybe some spacers, or use external software to tune it.
  2. This doesn't work, lights in stick never go out
  3. Doesn't work for me, what did you change? Do I need like larger view distance or something?
  4. As seen in the video. Switching to a unit first shows water, and then after going to map, and again to unit, it fixes itself. But 1st person aiming is broken. CA bug.mp4
  5. Just found this thread, this is such stupid idea, I wondered for hours why I can see as a spectator all units on the map, but not in the plane. This is game-breaking, since my server is designed to be a hard one, with no friendly units visible on the map. Now, it's just a possibility to cheat. Edit: apparently you can modify the settings, either set your own in settings, and then save the mission, or modify the values directly from options file inside MIZ, which it really a zip
  6. How is the thread going? SAMs still don't attack bombs, which is also an exploit on couple of servers, since you can just toss the bombs on pre-found targets, or from cover, and nothing can stop it from coming
  7. Mine solution was a corrupted drive. I noticed device manager refreshed on stutter, checked event viewer, which showed a CHKDSK being made, and also other event category showed lots of errors related to files. I did execuce a chkdsk fix, which fired after a PC restart, and then problem was solved, drive was a little corrupt, probably by a power outage, or some bluescreens which I had (NVME SSD). Interesting that I didn't see that problem in other games.
  8. phantom will take like 1-2 more years, so typhoon can take 3-5 from now
  9. Same issue, the shake makes weapons hit correctly, but it makes harder to identify everything. Also, sometimes it shakes less or more.
  10. I play on RTX 2070 super on Rift S, and I think it's minimum what you need, on bigger servers it kinda lags.
  11. We need something soviet, Su-24, or a 1st bomber in DCS, like Tu-22M, we have enough NATO stuff now, no enemies really to fight with.
  12. There were like 8 prototypes, not possible to make Ka-50N with limited data
  13. Yeah my bad, I meant soviet, of course there is no chance for a Russian one, but Soviet? Pretty old stuff
×
×
  • Create New...