Jump to content

dhevans79

Members
  • Posts

    103
  • Joined

  • Last visited

Posts posted by dhevans79

  1. That's right, and even though the potential is there, i havent been able to bring myself to sort through the mess and get to serious flying, learning and fighting. Getting the thing tweaked just right in both performance and controls is such a freakin hassle. And it needs to be done for two versions, and redone everytime something gets changed. blegh.
    I found creating a symlink for the settings folder indispensable for this. Set once in any version and it's instantly available in all versions. Instructions found somewhere in these mighty forums...

     

    Sent from my SM-N950F using Tapatalk

  2. Every week the Weekend Newsletter that gets posted to the site produces a notification for Tapatalk users like 5 or 6 hours before you can actually view the post. It's a weird Tapatalk thing. I never have the issue on PC.

     

    -Shadow

    I also get this "pre-notification". I always thought it was some kind of bug, but now hearing others also get it means I'm not going crazy :)

     

    Looking at the screenshots that have been posted recently, and the reduced chatter from the dev team, have been making me hopeful in the last couple of newsletters for some kind of announcement. Alas, no such luck yet...

     

    But I'm really looking forward to this :) Here's hoping for some good news this side of xmas.

     

    Sent from my E6653 using Tapatalk

  3. What do you see when you lool in the control panel settings for the joystick? Does it show the same behaviour as you describe in the aircraft? Or is this something that happens only when DCS is active?

     

    Is this behaviour only triggered once the SST is running, or will the joystick also behave the same when it has been killed?

     

    Any other settings or setup that we should be aware of when deacribing your issue?

     

    Sent from my E6653 using Tapatalk

  4. I tried many custom profiles, but found that the smooth profile by default is pretty good imho. Also placement of the camera just on top of the monitor bezel is best, with at least 30-40cm distance between the camera and the trackIr reflector at the closest point (when leaning in). Less than this, gave me jarring head movements where the head would suddenly block looking down right, or make 180 flips when trying to make fine adjustments to look at the controls.

     

    Hope this helps...

     

    Sent from my E6653 using Tapatalk

  5. Good day

    I had old pedals from thrustmaster (RCS) made of solid steel. I ve figured out that the X52 pots are really crap and I ve changed them for better ones. Eventually I ve ended up connecting the rudders to the X52 and blocking the yaw on the stick.

    You may save your pots for a couple of years buy using a spay (clean contact).

    Good luck.

    Hi TripleSeven.

     

    Any chance you could start a new thread providing info on how you changed the pots, or what you looked for when researching replacement pots. I wanted to do the same thing with my x52, but gave up as I have not enough understanding of electroincs to be able to decide what is required to source replacements that will work.

     

    I think that if the pots were replaced with quality equipment that doesn't judder like jelly in an earthquake, the joystick would be awesome...

     

    Much thanks in advance (if you do it :))

     

    Sent from my E6653 using Tapatalk

  6. Hey!

     

    Starting in reverse - the bug is there, but the update tomorrow should temporarily fix this - I changed the date of all the January missions to February (temporary, as I didn't adjust all the documents, so the date from FRAGO remains valid, it is just one system date that is different).

     

    Now as for the radios:

     

    During startup make sure that you enable both radios. Then leave RED radio (the top one) as is on CH1 until IP talks to the ground. Then before stopping short of active switch to CH2 to hear tower. After take off switch to CH4 on GREEN (bottom one).

     

    Your contact with the Lead is on TOP (RED) radio all the time, so don't change the freq there.

     

    For the moment to avert the January bug just use True heading and not Magnetic one on the HSI.

     

    And finally, make sure that you un-check the EASY COMMS in menu.

     

    Hope this helps!

     

    Ok, so in fact I was able to test tonight after all :joystick:

     

    Thanks for the feedback, very helpful.

     

    Having confidence in the setup, I left the green on CH4, and realised that the AWACS comms are not immediate, they are not triggered by the radio as like the flight lead when you start the mission. By leaving the radio on, in fact you just hear them randomly during the flight.

     

    Very Cool!!! :thumbup:

     

    Also, switching to true heading solves the issue for me, so after the touch and go, now I can bring myself around on the circuit by using relative headings to the runway, instead of flicking back and forth between the map view to see where I am going.

     

    Thanks for the guidance and support.

     

    Now on with the campaign :pilotfly:

  7. Hi all,

     

    I seem unable to hear the radio comms with the tower or the AWACS.

     

    When starting up, I don't hear the feedback from the tower when the flight lead asks for permissions to taxi / takeoff. I'm sure I heard it once, but that appears to have been by chance.

     

    I'm also having an issue when the flight instructor says to switch to channel 4 to hear the AWACS.

     

    If I change the bottom radio, I lose contact with the flight lead, if I change the top radio I don't hear anything.

     

    Could someone give me some clear instructions on how I should be configuring the radio panel to be able to hear all the communications I think I'm missing?

     

    Apart from the missing comms, I'm able to complete the mission, but from what I've read from the other threads, it seems like I'll need to do this later in the campaign too.

     

    Thanks in advance for any assistance.

     

    Loving the campaign otherwise.

     

    A second quick question, is the January compass bug still there or has it been fixed? I thought it had been updated already, but I still seem to have it. INS seems to be set correctly using the notes from the kneeboard..

     

    Sent from my E6653 using Tapatalk

  8. With the "APPATENT" launch of the F-18 ¿is held Q3 for the launch of the Av-8B N/A??

    no point releasing the harrier if there's no f-18 to run CAP ;)

     

    Sent from my E6653 using Tapatalk

  9. I have updated the version 2.0 to 2.1 I have gone 2gb update, and when I enter dcs I do not get the terrain of Normandy, it is more telling me to buy it and also leads me to a page in Russian, I have uninstalled the 2.0 And re-install again and come out exactly the same as any suggestions?

    still downloading update that I needed to force install by running command line. Splitting hairs here, but my update is 4416.9MBytes. If yours was only 2gb,do you need to try downloading the update again. If it was the right size, hopefully others can fill in the gap?

     

    Sent from my E6653 using Tapatalk

  10. just keep using the updater shortcut. keep opening it repeatedly until it updates. took me about 20 minutes. I'm downloading pretty well once. connected, but it would appear that the servers are a bit overloaded...

     

    Sent from my E6653 using Tapatalk

  11. looks like something funny.. it tells me that 2.0.5.3889.199 is up to date, but no terrain or purchased module for normandy available. :doh:

     

    will keep trying, but dcs keeps telling me no internet connection or nothing new...

     

    Sent from my E6653 using Tapatalk

  12. Ummm, I see a lot of people talking about backing on kickstarter or whatever. If I bought the map+assets in the sale from ED last month, am I still elegible to download tonight, or is this only for the kickstarter crew???

×
×
  • Create New...