Jump to content

Andurula

Members
  • Posts

    101
  • Joined

  • Last visited

Everything posted by Andurula

  1. "You are flying with partialy missing wings. There is still some lift and other forces acting, taking into account the changes in lift surfaces" I think it is fair to say that the modeling in DCS is complicated and sometimes these things happen in a simulation designed to run on consumer grade computers.
  2. And a quick video of what happens after the wings are ripped off. https://youtu.be/AZiNFXfvvVc To confirm, it is the wings coming off due to excessive forces on pullup. I can reproduce 10 out of 10 times. Load 4 Mk82's on pylons, roll into 30 degree dive, accelerate to 350kts, pull up sharply, (not sharp enough = no joy, pull up too sharp = you blackout and wake up to a spin) enjoy the ride. Last month I would usually feel a little "bump" and then look around to find my wings were gone. While trying to reproduce the last two days, the wings are departing about a second apart putting the aircraft into a wild yawing action. You can then straighten out with rudders and fly home without wings.
  3. Thanks for the reply. Happened to me again today except this time it happened when dropping practice bombs so I stand corrected that it is not blast damage that is causing the issue. I had practice bombs on the inner pylons and regular Mk82's on the outer pylons so I believe I am overstressing the wings on the pullout. I just reviewed the Tacview and it shows the aircraft being destroyed when the wings come off but continues recording ... nothing for another fifteen minutes while I flew back and landed. i wish I had the video just prior because the tacview file shows an IAS of 386kts just prior to breakup. Losing the wings at 386kts seems like something that should happen. Typyically, I begin my pullout around 325kts so not quite sure why the increased speed on the last run but I was adjusting parameters to tweak my bombing profile. I think the bug is that client doesn't recognize the aircraft has been destroyed and keeps on going. Both the track file and tacview file thinks the aircraft was destroyed. I am putting together a video file today and will upload it "soon". Tacview-20210120-102345-DCS-Iron_Bombing_Range_V21 (2).zip.acmi
  4. I am not sure if damage modeling is more of an ED controlled thing or something AvioDev is responsible for but I have managed to blow both of my own wings off several times now and still remain in control the aircraft. I have been exploring Mk82 dive bombing profiles in the C-101. Despite the dive tables in the Chuck's Guide manuals showing release altitudes down to 500 feet, I find sometimes when I release around 1000 feet agl or lower I take blast damage from my own Mk82's. The most common damage I receive is both wings get removed with flames coming out of the stubs. Oddly, while I do lose aileron control, I can control the bank just fine with the rudder. I get no warning indications on the annunciator panel and no sense that the aircraft is in distress. My cruise speed actually increases so I guess the model is accounting for the reduced drag. Under these conditions I have managed to continue flying for over ten minutes before returning to an airport and performing a sucessful landing. Seems like an awfully blatant bug to have not been reported but I haven't seen it anywhere. Unfortunately, the track files don't replicate the same result and I haven't had the video player running in the background to get a good record of the incident when it happens If it is useful I could get a live recording of the bug.
  5. After having a lot of issues early on with track files I have come to understand that the harder my computer is working the worse the track file is. Flying over the desert in the Persian gulf my track files are perfect. The harder my computer works to keep up with the graphics, the more likely a control input will fail to be recorded resulting in a bad track file. Flying over Haifa on the new Syrian map my track files are an absolute mess. Tips for better track files are, 1.) pick areas with low ground details on the map and missions with few units to control, keep your graphic settings manageable obviously. 2.) Never start on the ground in the parking area. A slight error recording a control input will mean you will never see your aircraft taxi accurately enough to make it to the runway. 3.) If you want to record a video off of your track files, better to make several short track files rather than one long one. That way an error recording an input early on does not corrupt everything that happens afterwards. Of course you could spend a lot of money on a top of the line computer which would also solve the problem. People with these sort of computers have been known to say, "there is no problem with track files, they work fine"...
  6. "Deflecting the control stick fully to one side makes the ball, in the slip ball indicator, slide completely to one side" Huh... that's definitely not my experience. From the front seat with no rudder input. https://youtu.be/RQpFVfv5iBI I haven't really compared to other DCS aircraft. I am just comparing to my experience flying actual airplanes. I have never flown a C101 or anything similar to it though so that is why I am just questioning it, and not critisizing it. It appeared like an aircraft with an interconnect system or SAS which is why I started asking.
  7. Well, yes, there is some adverse yaw. However it is so slight as to be neglible and from a sim perspective there is no need to add rudder input. That is what made me wonder if the C101 had an interconnect. I just went back to check. I am using the lastest open beta. My most violent aileron inputs barely gets the slip ball to touch the centering lines. From an external view, looking straight down, the nose deviates... 20-30cm? So, yes, you are correct it is modeled but it is very slight. I would have expected more from an airframe that is so short coupled. Thanks for the feedback. Still my favorite aircraft in DCS.
  8. The C101 module exhitibits virtually no adverse yaw in DCS. The slip ball does quiver slightly with a roll input suggesting something is being modeled but the effect is so slight as to be non-extistent. There is certainly no need to add rudder input when initiating a normal banked turn. I am curious, does the "real life" C101 have an aileron/rudder interconnect system of some sort or is this just a gap in the modeling?
  9. Yes, thanks. I was hoping to go a bit deeper than manual because the manual doesn't really cover much.
  10. Does anyone know of an english language source for explaining the navigation control in the Su-25 "A" ? If that doesn't exist is there anyone that can tell me the labeling for the lights on the control box? I think I understand, "start position", "destination airport", "approach mode" and the first four waypoints but that is only half of the lights on the box. Also, there appears to be only four lights for identifying waypoints set in the mission editor but if the mission has more than four waypoints, the system will continue to cycle me through additional waypoints as I overfly them. Is this normal in the -25A or has ED added the extra waypoint capacity that the real aircraft doesn't have?
  11. The F5 snakeeye data on the ED download site starts with a release interval of 100ms and goes up from there. |That interval results in some pretty tight spacing at 500 kts and 400 feet agl. Once I started releasing at 100ms interval or more I stopped blowing myself up. And for what its worth, max release speed of the snakeeye (by the book not what ED models) is about 550 kts if I remember correctly. The inflatable fin HD bombs can be released at a somewhat faster speed.
  12. Good tip on the sink rate. After some more digging I found some bomb tables for the F5E hosted on the Eagle Dynamics User Files download site. The minimum inteval the tables used was 100ms so it seems a reasonable limit.
  13. Thanks. You may have figured it out. An interval of 100ms seems to work but I have more testing to do.
  14. I am trying to ripple off Mk82 snake eye's but they are detonating immediately after release and long before they hit the ground. I assume its my setup but I am not sure which part. Does anyone have a profile that works for them or knows why I keep blowing my own wings off? Air speed around 500kts Altitude around 1000 feet Rippling a full load of 14 Mk82 Snake Eye at 20ms intervals N/T fusing set Single release Computer Target mode. From tacview it looks like the first two or three bombs release and then I blow up. Any thoughts? Is there a real world F14B manual that details this procedure? Thanks.
  15. Anyone familiar with using the C101 to move troops on the GAW/PAW servers? I thought I would try it but I can't taxi close enough to a logistics cache to pick up troops..
  16. Yes. Just copy your "Input" folder from your existing game and replace the OB installation "input" folder with the copied one. I find it useful to make a backup every week or two of my input folder "just in case".
  17. You know, this isn't a bad idea. I don't think I would pay much for it but I would definitely use it.
  18. Does anyone have any good DCS aerobatic resources to share? I can do most of the basic aerobatic maneuvers in the C101 but the vertical ones such as the hammerhead are a complete mystery to me. Pulling vertical, then punching the rudder at different airspeeds results in anything except a normal hammerhead. Any help or pointers would be appreciated. Thanks. Anything specific to the C101 Double Thanks. -Andu
  19. Thanks for the tip. I will give it a try. It occured to me later that I may have an AI issue as there are several AI flights in the background. I am going to test with a clean map tonight. [Edit] Just to follow up. The issue I was having appears to be a glitch with the AI. A waypoint command was causing the client to get confused apparently. Editing the command corrected the problem so I am happy to report I my issue was not with the Syria map.
  20. After about half an hour in mission on the Syria map the game goes into "slow motion". I will go from normal operation to suddenly 3 quick frames and then pause, another 3 or so quick frames and the pause. Aircraft is completely controllable since I have plenty of time in the pauses to adjust my controls and wait. This does not appear to be just an fps loss. I have experienced this with the UH-1H, C101CC and F14. Every time around 29 minutes into the mission. Happens every time. Flying low or staying high makes no difference. Kinda frustrating to spend half an hour waiting for it to bug out so I haven't troubleshot it extensively. The client is on an SSD with 32GB RAM. I5 and 1060i video card. I have not seen this issue on any of my other maps- Georgia, NTTR, Persian Gulf. I searched the forum and didn't find another report but I can't beleive I am the only one to have the issue. -Andu
  21. Are there any fourth generation modules that map well with the X52? I am realizing some of my frustration in learning the F16 is the struggle to map everything to my X52 Pro. The F16 relies on a lot of buttons on the HOTAS that I don't have and while it is certainly possible to use the X52 with this module I am thinking I would be less frustrated and enjoy DCS more if I wasn't trying to make the X52 do more than it was designed for. For the same reason, I love the Huey module and I think part of that is because of the simpler controls setup that require a lot less modifiers and non-intuitive button mapping to make work effectively. Do any of the later generation fixed wing modules work well with the X52? I know F16 isn't working for me. I suspect FA18 is the same. How about the F14? I am pretty sure the F5 would be a good fit but its older than what most other people are flying on multiplayer and I would like to be more involved with that scene. So, I am just looking for suggestions on what modules work well with the X52 until I can upgrade to the Warthog or something similar. Thanks. -Andu
  22. Thanks for the help but I think I figured it out while running through some more experiments I can drop singles of FAB100's at any time but I can't drop a single Mk82. I can only drop the 82's in pairs. Must be a weight imbalance thing. If I select a single Mk82 on the pylon it won't drop. If I select 2 Mk82's on opposing pylons they drop just fine. Thanks again for your ideas
  23. Thanks. I do that after every patch but for the past two I have had this issue. I have been dropping bombs in the C101 for a few months up until a few weeks ago but now they just won't release. Must be a weird keybind I haven't found.
  24. I recently switched back to OB. About two weeks ago I noticed my weapons release had stopped working. I walked through the steps in chuck's guide to drop a bomb and I went through my controls setup and everything appears to be working fine except bombs won't drop. Yesterday I believe there was another update. Still no luck with the weapons release but now my cannon won't fire. I used to be able to visually check the safety catch on the stick after using the trigger unlock control. Now I can't get it to flip to the unlock position no matter what I do. Has anyone else experience this? -Andu
×
×
  • Create New...