Jump to content

Floyd1212

Members
  • Posts

    1336
  • Joined

  • Last visited

Everything posted by Floyd1212

  1. I just checked for myself and also see the issue. Rocker down works fine. Rocker up slowly and it seems to be reliable, but click it too fast, and it jumps to Preset 1.
  2. Do you mean when clicking the rocker button with the mouse in the cockpit, or when using a bind on your HOTAS for those functions?
  3. I'm going to be honest, I did not read all 248 pages of this thread, but I did do a quick search for "S350" and didn't see anyone discussing the issue I am having... Some of the people that fly in my helo squadron are experiencing FPS issues when looking in the direction of an S350 site. The site is still 100km away, but frames drop to 10-15 fps when looking toward it, and come back to 60 fps when looking away from it. More than one squad-mate have described this to me. I don't see the same issue on my machine, but I have experienced issues after launching a Hellfire at the SR or STR from an Apache. I can spot the radars in the TADS and lase them, and everything is fine. But as soon as I rifle, my FPS drops to single digits for as long as the missile is in flight. Then when it destroys the target, my frames are back to normal. Anyone else experiencing FPS issues related to the S350 assets? EDIT: The next post from SizzlepopBACON is from one of my squadron-mates having the issue...
  4. To check if your boresight has been performed accurately, set your ACQ to TADS and tell George to slave to your LOS and see how far off the cued reticle is from where you are looking. If you have boresighted correctly, the dotted cross should alight with the solid cross exactly.
  5. It has done this for me since day one. You request repair and you get the 170 second countdown. At the end of the countdown when the actual repair starts, the helo levitates 3 feet off the ground and the access panels open up. When the repair is complete, the helo drops (literally) to the ground looking brand new. I assume it does this so that in the event you got repairs with any of the gear missing or damaged, the wheels are properly setting on the ground surface when the repair is complete.
  6. The laser on/off bug, and Geroge not ready to slave to PLT LOS, have both been fixed in the last patch for me. Try it in an Instant Action mission and post the track?
  7. Yes, if there is a way to reduce the saturation in the Moza software, that might work, but DCS needs to be configured for 100% saturation.
  8. Can you post a screenshot of your binds for the power levers, to and from Idle?
  9. We’ve seen this issue in missions on other maps when GPS is not available. I’m not entirely sure how this results in the symptoms you experienced, but forcing “Unrestricted SATNAV” in the ME solves it. I think there is a way you can save/edit the instant action missions to fix it yourself, but sounds like ED needs to address it in a future patch.
  10. Forgive me if I get my acronyms wrong, but what we are discussing (complaining about) here is the way the Yaw Channel of the SCAS is behaving when it is trying to help control the yaw of the aircraft. When you hold FTR for significant maneuvering, you are disabling (or at least reducing) the assist the SCAS system is providing, so of course you won't see the problem while you are holding FTR. What we are seeing (feeling) is overcompensation in the yaw channel when making small adjustments with the pedals while not holding FTR. For example, while rotating the aircraft to a new heading while in a hover, with ATT Hold enabled. Thanks!
  11. I like how the early results of the poll show 50% of users (4 out of 8 votes) are running a FFB setup. Sounds like a bunch of FFB elitists rushing in to make sure everyone knows how awesome their setup is. And yes, I am also running a VPForce.
  12. This may be related to the other bug of not being able to get the laser turned on from a cold start. If you switch to the front seat after letting George get his crewstation setup from a cold start, you see that he has the "grayscale" color bars up on the IHADSS. These color bars are turned on with the L6 button on the WPN page. If you turn this off, George will resume slaving to your LOS again. However, you can't get the laser turned on using L6 on the WPN > UTIL page. George says he is lasing, but the laser is not activated. Is it coincidence that he manages to get the color bars on from L6 on the WPN page during his startup routine, but can't get the laser turned on from the L6 button on the WPN > UTIL page? We have seen other bugs in the past where button presses on one page impact functions in the same spot on other pages.
  13. I totally get that there are a ton of variables and aircraft to test to make sure things are still working for each patch release, but there has got to be some sort checklist of the bare essentials that need to be tested before signing off on a patch. And you would think having George be able to rifle a Hellfire at a target would be on that checklist.
  14. That is probably just a DCS map zooming LOD anomaly. It also occurs on Sinai with parts of the Nile River Delta; when zoomed out they look green like land, then at some zoom step the land goes away and you see patches of water where they should be.
  15. Correct. Set the MAN range and you're good to go.
  16. It looks like when you edited the MGRS coordinates of your current position that come up in the KDU and changed them to the new coordinates, you didn't change the Grid Zone from 34W to 35W, and there is no MU within the 34W Grid Zone.
  17. Will it let you boresight again if you want to? Yes. Has it already been done for you? Yes. On a cold-start aircraft you will see the "IHADSS B/S REQUIRED" message at the lower left of the High Action Display until you perform the boresight. On a hot-start aircraft you should not be seeing this message.
  18. If you spawn in a hot-start aircraft, where the boresight is already done for you, is your gun accurate then? If you set your MAN to Auto it will do its best to calculate the range to the target based on your altitude and look-down angle, but it assumes you are on level terrain, so it isn't so good in hilly areas. I personally set mine to 500, and when I am in close to gun trucks and infantry, it is dead-on. Setting it to 1000 should give you similar results. I let George lase and "snipe" with the gun using the TADS if I want to engage something much further out. Can you record a quick track of your boresight procedure and share?
  19. It's flyable, for sure. I would not say that the change in yaw behavior is likely to cause anyone to crash into the ground. But it does impact slow speed hover taxing, aligning for rockets, heading changes while in a hover to engage a new target, trying to land on a small FARP pad, etc. And the sad part is that engaging ATT Hold isn't that much better as a result of the change that was made.
  20. And the even more obvious (and less subjective) bugs, like George's poor target tracking, and the ACQ not working when FCR is active, points to a clear problem. Not sure what the threshold is for deserving a hot fix after a bungled update like this, but I guess we didn't quite get there. I'm looking forward to these issues being resolved in the next patch... Right?
  21. Do you have a track file you can share of this (not) happening? From my experience, George will spot infantry just fine with the TADS when close enough, but there is some distance (unknown to me) where he won't be able to spot them.
  22. You may not be aware of the Coordinate Converter Tool by FalcoGer that helps with this type of setup. Not quite the same as doing it in the ME and having it already loaded in the aircraft when you spawn in, but you can capture all those points with the crosshairs on the F10 map, then hit "Transfer" in the tool and sit back for a minute or two while the data is entered in the KDU automatically. You can also save those coordinates as a file that can be distributed to other players for them to load into their aircraft. So these 8 coordinates captured in the tool: Become these points on the TSD: And I agree that having more navigation assistance from George would be nice to see in the future.
  23. Sometimes DCS will remap controls after an update, often for devices with axis that you never even intended to use that way. You can see in this screenshot just after you "lose power" your throttles have been pulled back to idle. That's when George starts complaining and tries to repeatedly arm the aircraft.
  24. George saying “Armed” over and over again happens when the aircraft loses power while he wants it to be armed. When power is lost, the aircraft is no longer armed, and he tries repeatedly to rearm it. This sounds like a binding issue. Maybe an axis on your pedals or an Xbox controller?
  25. I'm guessing ED is not advertising that the Apache can be flown solely from the CPG seat at this time. So, until ED fleshes out George as PLT to include startup and shutdown, your best bet is to get things up and running from the back seat, then switch to the front and go from there.
×
×
  • Create New...