Jump to content

Erk104

Members
  • Posts

    177
  • Joined

  • Last visited

Posts posted by Erk104

  1. I have been away from the M-2000C for a month or so. But have been impressed withe the improvements and upgrades. However I cannot align the ins as I did before it will not start the alignment when I do the posit verification in VEI the move to ALN. VAL is not lighting up nor is the align and alignment never starts. I am following the manual. Any help would be great. Thanks in advance. :joystick:

  2. Yes, especially since simulating the harness really doesn't work. You can still lean further forward IRL but the screen stops responding and just goes into a "wall". That's just an immersion killer. But I'm thinking the fix must be super easy, either for Belsimtek themselves or for us, if we're just pointed to where we can change it.

     

    The point I was trying to make with Razbam was they enforce a 8:00 realignment of INS even if power is connected during repair( because they have to roll you to the hanger) however that act is not simulated. So to be nice to everyone the add a menu option to turn on or turnoff the feature this made it acceptable in almost all communities.

     

    I really do hope BST does this with f-5e as well. A menu option to see if you want your track ir limited by seat belts.

  3. I just bought the F-5E and realized quickly that it suffers from the same problem as the F-86, and that is a very limited amount of movement in the cockpit before you hit the invisible wall (this applies to TrackIR and VR users obviously). This means that you can't lean in and check gauges and even worse is trying to hunch down to look at switches on the left and right side consoles. I really don't know what purpose these "walls" serve, since EDs own modules are not nearly as restricted. Please Belsimtek fix this, because as it is now it makes the module pretty hard to use. Constantly zooming to check things is not really an option I think.

     

    I couldn't agree more there are time when a simulation purposely inhibits actions that don't seem necessary set lets limiting eye movement is one of them however belsimtek is not the only one. Razbaam is doing it too with the m2000.

     

    It is impossible to simulate everything. So why try make the game playable it Already has tons of draw backs in the game why simulate a seat belt?

  4. I was playing last night in NTTR server. I was loaded with Bombs. Prior to take off I set my depression for Manual mode on the sight for the bombing run I planned to make (60 MILS). Once selected I checked the Depression to ensure it set and it was. You could see the Sight drop to the bottom of the hud glass when going Manual mode.

     

    Next I took off for target area to find there was air threat there. I switched to MSL and turned on my guns and Missile Master Arm. I then turned toward my base and egressed to evade a Mig-29 threat. During the flight back to base the Sight pipper would got go back to depression setting I previously set which was 60. The sight maintained the MSL setting even though I switched to Manual. I tried to change the MIL setting while in Manual mode and it would not change. I even did a repair back at base and it still wouldn't change the only way to correct the issue was to get a new jet.

     

    This is a real problem with the F-5Es ability to switch from Air to air to air to ground.

     

    BST please fix this issue.

  5. I'm starting to wonder if there's a difference with 1.5 vs. 2.0 NTTR. I didn't have many problems killing ground targets in 1.5, but in NTTR, last night, we put about 170 rounds (confirmed in TacView) of combat mix into a DogEar Radar, and it didn't blow up.

     

    In the past, I've run AP, HEI, and CM, and been able to kill a DE Radar with one of two passes. Not sure if I'm just really inconsistent, or if there's a significant difference in armor on the front/back/sides/top of the radar. I wasn't very consistent with my approaches in terms of aspect front/side/rear, but there were enough 20-30 dives that at least a fraction of the shots should have been hitting the top.

     

    I had the same issue with NTTR. I normally fly NTTR F99. There are few 1.5 I frequent but they are mostly Air to air servers. Sounds like there may be issues with NTTR and air to ground guns.

  6. I'm starting to wonder if there's a difference with 1.5 vs. 2.0 NTTR. I didn't have many problems killing ground targets in 1.5, but in NTTR, last night, we put about 170 rounds (confirmed in TacView) of combat mix into a DogEar Radar, and it didn't blow up.

     

    In the past, I've run AP, HEI, and CM, and been able to kill a DE Radar with one of two passes. Not sure if I'm just really inconsistent, or if there's a significant difference in armor on the front/back/sides/top of the radar. I wasn't very consistent with my approaches in terms of aspect front/side/rear, but there were enough 20-30 dives that at least a fraction of the shots should have been hitting the top.

     

    I had the same issue with NTTR. I normally fly NTTR F99. There are few 1.5 I frequent but they are mostly Air to air servers

  7. I have noticed with this simulation that air to ground guns are practically useless against soft skin targets such as SAM radar instillations or lightly armored vehicles.

     

    I rolled in 5 separate times on a SA10 radar sight after it exhausted its supply of missiles and I was unable to destroy the radar with 20mm guns. I know there is a difference in AP rounds vs HE rounds however I was using a Combat Mix and I feel that that the potency of the 20mm gun is weak at best. I have had no problems air to air with the gun but definitely weak when put air to ground. This is a definite draw back. I hope that developers will give the guns a little more bite. especially when it comes to light armor.

     

    Armor Piercing rounds is a MUST for tanks and armor however trucks and light armor should bow to a 20mm combat mix.

  8. My issue was this.. my first load out was rockets I fired them and rtb loaded with Bombs... returned to the battlefield I released them no issues. then rtb again reloaded with Rockets again. This time they would not fire. I dont' recall going to DM or DG at anytime during the flights but I could have I guess.

     

    Regardless I am certain there is an issue here.

  9. There is an invisible wall- your straps holding you to the seat. It's not a bug it's on purpose. That's why we have a zoom button

     

     

    Sent from my iPhone using Tapatalk

     

    the reason we have the zoom feature is so that we can move our head forward and see things more clearly... in real life the naked eye has much better depth but the resolution of screens cannot simulate reality to accommodate that we have be able to zoom.:)

  10. Have you remembered to put to turn off the Jettison Selector Switch again.

     

    Since if its in any position other then the Safe/off (middle) position you wont be able to launch your missile.

     

    Since usually you will jettison your external in a hurry before combat so you might have forgotten toswitch it back to the middle slot

    (thus preventing the launch)

     

     

    I too have had problems getting the Sidewinders to launch and after reviewing track files I found the above to be my problem. I am loaded out for air to ground then I got jumped by a Mig 29. I jettisoned my load and evaded a missile shot and caused him to over shoot. I was in perfect position for a classic rear aspect sidewinder, got a good high pitched tone, pressed the launch button to no avail nothing. I switched to guns and managed to take out one of his engines but I had to egress as he was getting help from other aircraft. I bugged out and then went and looked at the track files to find out what had happened.

     

    When I jettisoned my ordinance I failed to put the selective jettison back tot he center position. I went in and tested and this does cause the sidewinders NOT to fire. I am better educated now.

  11. Yep, trim is not working for me at all, I did a straight and level at constant speed, and ran the trim to its maximum positive and negative value, and the aircraft didn't move at all. I run a Logitech G25 with FFB for Assetto Corsa, and use the pedals as rudders - I think it's probably the FFB on the wheel, but I'm not sure how to fix it without disabling the wheel FFB entirely, which will affect its usage in other games.. any suggestions?

     

    Highlb, I have a g25 Logitech to and use it just like you do thiisfixed the issue.

     

    Go to run on you computer type in regedit then follow these instructions:

    I found the issue on my side. I was using a virtual joystick driver which has the force feedback property. I used this registry hack to remove the force feedback property: http://vjoystick.sourceforge.net/site/index.php/forum/5-Discussion/1149-solved-disabling-force-feedback-support#3674

     

    Edit: You can check the dcs.log if a device with force feedback capabilities was detected!

     

    I am not a computer programmer however I do know that the regedit function can really break a computer unless you know exactly what your doing. My question is if I remove these and I find out that this is not my problem how do I get these back in?

     

    Just rename the entries :) e.g. add '_' before the name

     

    This has fixed my problem. Thank you f4l0

  12. I found the issue on my side. I was using a virtual joystick driver which has the force feedback property. I used this registry hack to remove the force feedback property: http://vjoystick.sourceforge.net/site/index.php/forum/5-Discussion/1149-solved-disabling-force-feedback-support#3674

     

    Edit: You can check the dcs.log if a device with force feedback capabilities was detected!

     

    I am not a computer programmer however I do know that the regedit function can really break a computer unless you know exactly what your doing. My question is if I remove these and I find out that this is not my problem how do I get these back in?

     

    Just rename the entries :) e.g. add '_' before the name

     

    This has fixed my problem. Thank you f4l0

  13. Do You have any FFB device plugged in You computer? Because if You do, the infamous trim bug will affect many (though not all) planes no matter if FFB in options is set to "on" or "off". With both previous Belsimtek planes affected by the bug, I'd guess F-5 is too. That's more general DCS problem, though.

     

    I have almost all modules with the exception of the WW2 planes. And the F-5E module is the first I have seen of this issue.

     

    to further trouble shoot I disconnected my Logitech FFB racing wheel and pedals and mapped my Twist stick to my rudder controls. This did resolve the issue however now I MUST fly with the twist stick instead of the pedals which I do not want to do. I wish they would implement a FFB disconnect option that would fix this issue.

  14. I found the issue on my side. I was using a virtual joystick driver which has the force feedback property. I used this registry hack to remove the force feedback property: http://vjoystick.sourceforge.net/site/index.php/forum/5-Discussion/1149-solved-disabling-force-feedback-support#3674

     

    Edit: You can check the dcs.log if a device with force feedback capabilities was detected!

     

    I am not a computer programmer however I do know that the regedit function can really break a computer unless you know exactly what your doing. My question is if I remove these and I find out that this is not my problem how do I get these back in?

  15. I reckon it is the implementation of ffb-capable hardware/driver and what dcs expects from it. I've written a little about it yesterday with added possible solution today, but that is up to ED coders to implement or not. http://forums.eagle.ru/showpost.php?p=2850891&postcount=13

     

    We can only work around by disabling the device or removing the ffb-capable flag from the driver. However doing so will almost certainly result in loss of rumble/vibration effect on direct input device. Still, trim is more important feature imo.

     

    I wonder, anyone here with Jetseat rumbler have these issues too?

     

    My problem is I a have FFB racing wheel that I only use the pedals for the rudder so the game believes I am using FFB so no matter if I turn FFB on or off it has no effect on the trimmer.

  16. I am using Logitech Racing wheel FF ( I only use the Pedals for rudders and the shifter for extra buttons) and a Saitek X52 for my joystick and throttle. I do have the trimmers mapped to a coolie hat buttons on my joystick, they are set as follows in my controls:

     

    Aileron Trimmer Switch- Right Wing Down

    Aileron Trimmer Switch- Left Wing Down

    Aileron Trimmer Switch- PULL(CLIMB)

    Aileron Trimmer Switch- PUSH(DESCEND)

     

    Because of the previous Post by wumas0201 in which the FF back actually helped resolve his issue I tried to do it with my configuration but it did not help. The Hat switch has no effect on the trim. I can hold it down and the Gauge on the upper left dash goes all the way to the 10 and stops but the plane does not trim at all. The trimmer button on the joy stick also moves as if its trimming but the trimmer does not effect the plane's flight.

     

    Any assistance would be appreciated .

  17. Trim Problems

     

    I am having trim problems. In talking to fellow pilots they say the Joy Stick and the Trimmer are connected win maneuvering. However mine are not... see the picture attached.

     

    What happens is I trim and the little Diamond moves to adjust but the big diamond continues to do its own thing and the Big Diamond is what is controlling the aircraft so essentially I have no trimming... the buttons work but they are doing nothing.

    140541621_Trimproblem.png.11629b6e903bd23078df01e66835ea32.png

  18. AWESOME... the long awaited CCRP Release Thank you Zeus :thumbup:

     

    PS.. I was really getting pretty good at hitting the button when the Queue passed the release point...

  19. sorry for this question but i'm pretty new of dcs....... when i click with the mouse on mirage cockpit , for example radar switches or ins switches nothing happens.....what am i doing wrong ????

     

    Try doing a Left ALT+C this should enable a clickable mouse.

  20. Why do you want to bother with alignment if you do a 3mn turn around ?

    It's not even the time to refuel. So why do you want to enforce alignment in this type of game ?

     

    It just strikes me as contradictory to perform 3mn rearm and repair and ask for realistic procedures ! But that's just me, it doesn't matter...

     

    Because after having a missile thru my wing I want to get back up there and get some pay back not wait 3 minutes then another 8 minutes for alignment. :thumbup: I do understand the options selection for Gyro Drift and Alignment these will work it just doesn't seem intuitive. It makes sense to me to connect GP and keep the INS aligned while the repair is happening. Then the Gyro Drift and Alignment options wouldn't be needed (even though its not realistic to the real aircraft, its equally so for the 3 minute repair which happens without having Options selected).

     

    I didn't mean to take way from ZerO_Crash's discussion.

  21. You have the choice, on your own, to enable or not INS alignment and/ or Gyro drift (options menu/ special tab)

     

    Then the mission designer can let you play with your settings or enforce INS alignment AND gyro drift.

     

    In case of alignment you have the choice to do different types of alignments.

     

    So it seems you already have the choice. Isn't it ?

     

    You are correct I do have a choice.

     

     

    I think you have a great sim but the INS realignment issue with the way the manual reads seem counter productive. Again just my opinion... I think a ground power connection to keep the INS aligned (even though not realistic to the real aircraft), seems more in line with the 3 minute repair of an aircraft(also not realistic to the real aircraft).:)

×
×
  • Create New...