Jump to content

razo+r

Members
  • Posts

    11429
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by razo+r

  1. 1 hour ago, markturner1960 said:

    Do you think that it is because I am within 10 miles of the JTAC that I am not getting the options? Watched a Grim reapers tutorial and in that he mentioned you dont get IP Inbound until 10 miles.....I am starting well within that.....?

    In which case is it possible to get the target lased by a JTAC without starting greater than 10 miles out? 

    If that were the case, still does not explain why they dont reply in the small test mission I uploaded earlier though.... 

    Edit, no its not, moved my apache to 12 miles away, JTAC still wont respond when called

     

    Distance has nothing to do with it. You can get tasks way outside of 10 miles, not sure about specifically the IP Inbound call though. 

    In the mission you attached, you didn't set it up properly.

    You gave him the FAC task, but set him up behind a mountain, unable to see anything to FAC. Thats your main problem.

    And a tip, try to avoid double tasking. Like for example you set him first to FAC on frequency 133. Then you gave him the task to set frequency 131, and then in another task you gave him the task to set frequency 133 again.  It doesn't harm, but try to avoid it. You never know how fragile DCS is. 

    So in order to fix your mission:

    Place the JTAC somewhere with a line of sight to targets (and perhaps set him to invisible) -> Your main issue in this example

    After that he should talk to you just fine.

    I've tried it with the A-10C and it works. No idea why the AH-64 refuses though.

    • Thanks 1
  2. Just google... If you have more specific questions, you can always come back. But asking "how to navigate" is simply lazy, IMO. 

    Look for VFR / IFR procedures, look into the manuals for navigation equipment, search for these on youtube/google. It's all out there.. 

    I mean, you don't even tell us which aircraft. Navigating in a FW-190D is substantially different compared to navigating in a F-18 within IMC. 

    Oh and don't expect a single 12min video to properly explain everything. If you want to do proper navigation, it will take hours of practise. 

  3. The only thing you could do is load the mission you plan on joining in singleplayer, fly it for a bit and then check in the MP server selection screen if the IC got triggered or not. 

    Sometimes a simple restart of DCS will solve the issue, sometimes not. 

    The IC has been not working as designed for an eternity and there does not seem any intentions of solving the issues. You just have to live with it and hope the IC has a good day. 

    • Like 1
  4. Just now, Schmafuzius said:

    thats what I thought should happen, but somehow if I would just increase rpm to 101% rpm and do nothing else the Apache will spin and tip over in a matter of seconds... it really is frustrating...

     

     

    Have you made sure that the collective is all the way down? 

    Have you also made sure the easy flight or simplified flight mode settings are turned off? 

    • Like 1
  5. 7 minutes ago, Schmafuzius said:

    Thx for your reply.. I will upload a trackfile maybe i really do something wrong..

    Regarding the 95% I  forgot to put the "rpm" there.. So when I start up after both engines are running I am supposed to increase rpm to 100% (or even 101%) with no collective but then the helicopter already moves a LOT

    I never really had a look on my actual weight I was just doing Instant Action - cold start on a random map.. not sure how big the loadout is there....

     

    EDIT: I checked the bindings already but maybe I missed something - will check again.. thanks

     

    The heli should not move if you increase the rotor RPM to 101%. If it does, make sure your wheel brakes are set and your collective is all the way down. 

    • Like 1
  6. 8 minutes ago, Schmafuzius said:

    Hmmm.. please let me know if you find out the reason..

    I am struggling with the AH-64 aswell... as soon as I get up to  ~95% it starts moving and I have a really hard time trimming it out..

    I keep crashing the AH-64D like 9 out of 10 attempts during take-off.. maybe I am just to stupid for helicopters...

     I am using the TM TFRP at the moment, I already considered switching to other rudder pedals (maybe the new WinWing??) but I dont think that that will help with my obvious lack of skills 

    First of all, consider taking less weight with you. The lighter your heli, the more reserve you have, unlike at 95% where you are almost at max... 

    Then, make sure your axis assignments are set up correctly and no double bindings. Also make sure the axis curves, if needed, are reasonable. 

    And if still all fails, feel free to upload a short track so we can give you exact inputs and not just random, general guessing. 

  7. 1 minute ago, WolfyDHowler said:

    Same issue happened to me, with my Sptifire in "Beware! Beware!" campaign.
    Was running the engine on optimal RPM (no further than 2850) and it happened while cruising.
    I was on 21.000 feet, 2650 RPM, +4 Boost when the engine just shut down out of the blue. Not even in dogfight.
    In the aftermath was saying "Engine #1 Degraded".
    Track file uploaded.

    spitfire_engine_degraded.trk 49.06 MB · 0 downloads

    Did you clean the spark plugs from time to time? 

    Oil and water temp within limits? 

    Proper warmup completed and oil pressure within limits? 

  8. 1 minute ago, Landei said:

    Ich hab auch mal wieder was ...

    Wenn ich beim Rumflattern die Karte einblende, öffnet sich das Mistding immer mit einer starken Vergrößerung. Die drehe ich dann mit dem Mausrad wieder auf ein erträgliches Maß zurück und erwarte, dass sich DCS das merkt. Macht DCS aber nicht. Beim nächsten Öffnen ist die Karte wieder auf Grashalmniveau vergrößert und nützt mir rein gar nix.

    Frage (völlig überraschend): Kriegt man DCS irgendwie dazu, sich die eingestellte Kartenvergrößerungsstufe zu merken?

    Beim ersten Öffnen der Karte übernimmt sie den Zoom, welcher zuletzt im Missionseditor eingestellt war zum Zeitpunkt des Speicherns. Danach sollte es dein Zoom übernehmen.

    • Like 2
  9. 7 minutes ago, Supercharger said:

    Moin, kurzer Themenwechsel,

    folgendes Problem: 

    Bei schnelleren Sichtbewegungen im Cockpit(TrackIR5) bilden sich horizontale Linien heraus, ansonsten sieht die Grafik  sehr gut aus und läuft flüssig.

    Ich habe die Grafikeinstellungen auf "Hoch", die Hardware sollte auch nicht das Problem sein(RTX3060). Ich weiß nur eben mit diesen ganzen lustigen Grafikeinstellungen wie SSS,SSAO oder SSLR nicht viel an zu fangen.

    Weiß da jemand Abhilfe??

    Du meinst wohl screen tearing?

    Das ist normal wenn dein PC mehr oder weniger Bilder in der Sekunde produziert, als dein Bildschirm darstellen kann. 

    Dieses Phänomen kann durch V/GSync in den Grafikeinstellungen vermieden werden. 

    • Thanks 1
×
×
  • Create New...