Jump to content

PiedDroit

Members
  • Posts

    1610
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by PiedDroit

  1. It's a beta, not all features are available.
  2. Or the Murage
  3. Is it possible to do in flight alignment using a visual reference (since there is no GPS to it like in the a-10c)?
  4. :megalol: No, I was trying to find the reason why he posted USA! I'm such a fool, this thread has so many updates that the answer lied in previous page already :music_whistling:
  5. This?
  6. Hello, you can use the search function on the forum to get some insight (advanced search, "mirage vs", for example). Check this one for instance (one example): Mirage 2000C Tactics
  7. Will there be an option not to use the button? Without any timer or whatever, just get max G when going to full range? In my case the full range is already hard to reach, I don't need a button on top of that, would be nice to have a choice. Thanks
  8. I was thinking about MiG-21bison too, should have said "different version". And yes, would be nice to have :D
  9. Dorsal fin ? (Guess) Really I don't know either and I want to know too!
  10. Bis not Bison, different aircraft ;) Mmanual is here: \DCS World\Mods\aircraft\MiG-21BIS\Doc I suggest flying the traning missions as well (from main, menu, TRAINING-> MiG-21bis). Happy flying :thumbup:
  11. You're fast, I was about to suggest that :thumbup:
  12. Let's use different denominations then, StrikerViggen and FighterViggen. Wait, too long to type. I don't think it's only confusion though, in my case even if I *know* it's a strike aircraft I can't help thinking about pitting one against a MiG-21BIS :D
  13. When you write a PM, at the bottom of the screen you can tick the box manually too (the setting in user CP will make it ticked by default I think): Miscellaneous Options [ ] Save a copy of this message in your Sent Items folder.
  14. Hello, the TrackIR reference (within parenthesis) was made to illustrate the fact that IR camera tracking had problems on it's own and I was asking if those issues were not existing with Oculus Rift's tracking system which is using the same kind of technology. I think I was clear enough on that. Anyway, for the sake of clarity I will reformulate the questions: Did anyone using Oculus Rift had any problems with the Oculus Rift tracking system regarding: - Multiple Oculus Rift users in the same room? - Light interference that would cause problems to the Oculus Rift tracking system (which happens to be of infrared type and thus possibly subject to interference from other light sources such as sun and/or artificial lights)? Thanks
  15. I know that thanks, read again, questions are for the Oculus Rift tracking system (in Oculus Rift thread) :P
  16. Hello, I have some reserves concerning the IR camera tracking, maybe Rift users have some answers already (or maybe it was already posted): - Multiple users in the same room? - Light interference (which is really problematic with the TrackIR for example)? Thanks
  17. After thinking too, maybe the max force (hard stop) should be engaged as soon as the stick is pulled to max deflection. And back to elastic force after a set time. Here's my reasoning: If the pilot needs max input, he need it maybe NOW, and most likely he's able to pull the 40kg right away. However he's not superman and after a set time, the stick goes back to elastic stop, until the pressure has been released on the stick (another threshold, close to neutral), allowing to repeat.
  18. I'm not a big fan of the button, this would be very strange... I like option 2, although I think should be the other way around too, release the maximum force after a set time (you can't keep those 40kgs forever ;)).
  19. You forgot to tell the Vive version he tested was a dev version (he mentioned it during the video).
  20. Is there a big drag penalty for the Éclair pod? I suspect this pod will quickly become standard equipment if there's no downside to it :D
  21. PiedDroit

    Chaff bug

    It really seems to be a bug, I noticed it too (actually I wanted to start a thread about it when I saw this one). Here's a track I made using 1.5.2.48162, from the mission editor I equipped ASO pods and missiles, 16 flares / 48 chaffs, starting in flight. I removed the ASO cap then switched to external view and kept the release button pressed (I replayed the track it worked for me). It's clear that we see 16 (8x2) flares released along with visible chaffs then nothing. If you equip chaffs only, nothing will be released at all. NoChaffs.1.5.2.48162.trk
  22. Probably the same (if they every flew a non-FBW aircraft). However, in terms of training and combat effectiveness FBW is a huge improvement, since pilots can concentrate more on SA and weapon employement, rather than flying the aircraft (not even counting the benefits of relaxed stability). A guy like him is one in a million (edit: I mean a guy able to master his aircraft like this)... It's the same with computerized engine control, you don't have to worry about radiators, air intake pressure and whatnot :D
  23. It seems that the "width" and "height" parameters are used in wrong calculations. On top of that, the mouse does not seem follow the same logic, which makes configuration impossible: For example, on a 2560x1080 screen, using the following config files, the "Exit" button is highlighted by the mouse. Version is 1.5.2.48162 Offsets on pictures are 0-based: _ = function(p) return p; end; name = _('1 Screen, GUI(center)'); Description = 'One monitor configuration, GUI centered' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } local wGUI=1024 local hGUI=768 GUI = { x = screen.width/2 - wGUI/2; --768 y = screen.height/2 - hGUI/2; --156 width = wGUI; --1024 height = hGUI; --768 } UIMainView = GUI _ = function(p) return p; end; name = _('1 Screen, GUI(center)'); Description = 'One monitor configuration, GUI centered' Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect; } } local wGUI=1024 local hGUI=768 GUI = { x = screen.width/2 - wGUI/2; --768 y = screen.height/2 - hGUI/2; --156 width = screen.width/2 + wGUI/2;--1792 height = screen.height/2 + hGUI/2;--924 } UIMainView = GUI
  24. PiedDroit

    S530 Range

    Thanks, I get what you mean now :thumbup:
×
×
  • Create New...