Jump to content

primus_TR

Members
  • Posts

    199
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by primus_TR

  1. Strike Fighters 2 is helping a bit with the f4 itch, but for how long? Damn, this will be the best module ever.
  2. I'll be damned. Never would have suspected the wheel. Deleted the darn dll and the problem resolved! Thank you much !
  3. Hello, thank you. I have a budget steering wheel, could that be i? I have no other controller attached that has force feedback. What do you suggest I do? Just delete that dll or completely uninstall the driver for the wheel?
  4. Hi, after the latest update, DCS no longer works for me. I get the following window. This happens every time I try to run the game. My crash log is attached. Any help would be greatly appreciated. dxdiag.txt dcs.20231118-145001.log dcs.20231118-145001.dmp dcs.20231118-145001.crash
  5. This exchange has become irrevelant to the topic at hand, but just to indulge you one last time: I never said anything about mistakes or poor wording in the manual. Those are your words. On the contrary, KA50 has a particularly well-written manual. But sometimes the reader may need a little more familiarity with ED's style to tell what exactly is modelled, and what is not from the information provided in manuals. The fluctiations you'd see in compass during flight, not only in mig21, mi8, but in all the other modules (assuming that you are actually referring to the compass, and not the HSI), will be due to bank or pitch angle, and will settle down after coming back to level flight. Since we were talking about INU alignment on the ground, I don't see how it is relevant In any case, magnetic deviation due to interference from metal objects is not modelled in the game. but believe how you wish, false as it may be. I explained you a method to very easily verify it, but obviously you have no interest in such verification. And as regards your other irrelevant (to the topic at hand) comments, I'll let you believe what you want, facts notwithstanding. I'm not interested in further exchange with you. Have a great day.
  6. I'm using an old Saitek X55 hotas. A controller USB issue was my first thought also, but I checked controller settings and my controller was working normally. And also, the keyboard flight controls were not responding also. So, I think controller can be excluded as a source of the problem.
  7. Not to be argumentative, but the manual also contains general information about the systems for information only, and not all of them are modelled in the sim. Believe me, I've been around since Flanker 2.0 times (way before LoMac), and had Black Shark since version 1, and I can assure you that magnetic interference from metal objects is not modeled in this sim. You can easily verify this: bring your mobile phone closer to the compass and see if it causes interference (joke). Seriously though, to test this, you can set your chopper close to another chopper (a huge metal object that should normally cause magnetic interference) and see if the magnetic compass moves or is disrupted in any way.
  8. Unless power lines or very large metal objects are close by, metal objects within the aircraft are more relevant for magnetic compass correction. There is no downside to using magnetic inu adjustment when on the ground as long as you've not landed on a big metal ship or sitting under power lines. In any case, magnetic interference from metal objects is not modeled in the sim, hence a non-issue
  9. In the general game settings, set avionics language to English. Changing cockpit language only changes cockpit labels. Avionics language in the general game settings is what you need.
  10. Actually, I was looking to find info on whether ED made an announcement as to why they are revising the engine model, and what specific changes they intend to introduce by revising it.
  11. As of now (after ~24 hours), authentication is still not working and forcing off-line mode. Any timeline on when this will be fixed?
  12. What specific improvements/changes has the new engine model introduced over the former one? The changes I have noticed (by casual observation): 1. Higher torque is needed now to maintain an off-ground effect hover (a bit less than 40 psi compared to around 30 in the former model), making it very difficult to rotate left in a hover (full left pedal barely enough). 2. EGT can get very high at startup, if you're not slow enough when throttling up. 3. Fuel consumption has increased two-fold. (back to normal after the last patch). 3. Top speed seems higher now, especially up high. Anyone noticed other changes? Is there a list posted by ED somewhere of the changes?
  13. Login still not working But at least it now lets me play in offline mode, i.e. I can use my modules
  14. I'm looking for a program that can work with windows joysticks, which will take raw output from joystick axis input, dampen it, or average out the input values, and output the modified value. The purpose is to get rid of curves, and have a linear but dampened (adjustable) output, kind of like an PID controlled, to average out values over a set time. (e.g. take average of the inputs from the last 0.01 milliseconds and output it). I'm thinking this could be a better way to emulate a tall stick. Is anyone aware of such a program which is compatible with windows controllers?
  15. I know this is an old post, but if you or anyone else is interested, I used winch grease, the kind that you use in winches on boats, to get rid of the friction. I applied plenty of it both underneath the circle base which supports the spring, and into the gimbals. Worked a charm. Any non-corrosive grease should work, I suppose.
  16. In my case, keyboard controls stop working also, so it must be a different issue.
  17. Due to the torque and fuel consumption issues with the latest engine modeling, I am using the old flight model: /FMOOptions.lua New_engine_model = false Unfortunately, I do not know what exactly caused the problem so it is not something I can reproduce at will; hence, I can only submit a track in which it occurred when it occurred, which was after about an hour into the mission. The reason you cannot reproduce is probably because the track was recorded using the old flight model. If it will be of any help, I can rerun the track on my end and record a video of it. It is bizarre: Cockpit instruments showing straight attitude. External view showing ~40 degrees bank, 20 degrees pitch up, heli flying straight without loss of altitude. It won't accept flight control inputs (neither keyboard nor hotas), but cockpit systems remain interactable. Anyhow, I believe this is a significant bug, that's why I took my time to report it for I want to see this module reach perfection. So, do as you wish with this information. Ciao, Calabrone. Il consumo di carburante e i problemi di coppia con la nuova modellazione del motore rendono spiacevole far volare l'Huey in questo momento. Ecco perché sto usando il vecchio modello di volo. Non intendo utilizzare il nuovo modello di volo finché non risolveranno i problemi. Ciao
  18. Well, very refreshing to see a track-documented bug report being ignored.
  19. I started having this very strange bug; it is not easy to describe but I'll try (track is attached): On Caucasus map, using MT version: 1. Heli becomes uncontrollable, as though I plugged off my HOTAS. The joystick controls are normal, though, as they work normal in the settings/axis controls page and keyboard flight controls also do not respond. 2. All buttons in the cockpit are clickable, radios work etc. 3. The heli is stuck in an impossible attitude (50 degrees bank, 20 degrees pitch up) yet maintains level flight. 4. Weapons fire, but after a couple of rounds, tracers disappear. Same with flares. I can hear the flares shooting, but no flares show. 5. ESC menu works, I can exit the mission. I can also exit the helo by ALT+J. Track is attached (a long flight, an hour+). The problem occurs close to the end of the track. Note: I'm using the old flight model. This happened twice when flying a Briefing Room-generated mission. Not sure if it is possible for a mission to break the aircraft dynamics like this, though. I have never before encountered this bug. It may be somehow related with the co-pilot autopilot. Both times, it happened when going back and forth from the autopilot. uh1_out_of_control_bug.trk
  20. This, plus too much head wobble and too much left pedal needed when hovering and taking off.
  21. Both methods (overflying and Shkval) work for me, except when using Shkval for INU alignment, it must be locked on to an object (TA must appear). You cannot just point it to an empty field, lase and use that location; there must be an object (a building, vehicle, etc.) that you can lock on and TA must show. The overfly method works perfectly. You might want to review your steps.
  22. It could be a heading alignment mishap. You're not inadvertently flipping the mh/gyro/man switch while hovering by any chance, are you?
×
×
  • Create New...