-
Posts
1004 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Everything posted by EasyEB
-
This has been reported. Look at the bugs section.
-
[REPORTED]/[MERGED] Roll Oscillation w/ AP Alt Hold - 1.5.6.3690.269
EasyEB replied to Scotch75's topic in Bugs and Problems
Yes. https://forums.eagle.ru/showthread.php?t=186573 -
Thanks! By the way, this is for both current installs (1.5 and 2.0).
-
Yeah, let's hear it!
-
Thank you for taking the time and looking into it.
-
Ok, here are tracks from version 1.5.6.1938.247 where the swaying is not present, and version 1.5.6.4546.280 where the swaying is present. I also shot video of the two version where I try to execute the same maneuver so the swaying is comparable. In the videos, note the swaying of the aircraft when banking in to a turn, and when straightening out of a turn. Also note how long it takes for the gun cross to stabilize after rolling in on the X on the ground. DCS version 1.5.6.1938.247 - before the swaying was introduced DCS version 1.5.6.4546.280 - after the swaying was introduced See tracks from the two versions in the attached files. No mods used. No input is made other than the stick. 1.5.6.1938.247_swaytest.trk 1.5.6.4546.280_swaytest.trk
-
Since update 1.5.6.3690 the A-10C has become sluggish and more unstable when turning or making sharp maneuvers. The plane acts as if the center of gravity has been pushed back and the plane sways back and forth when making sharp maneuvers. This is related to the altitude hold issue reported here, as both were introduced at the same time and is possibly related to each other: https://forums.eagle.ru/showthread.php?t=185536 But even though the autopilot altitude hold issue was resolved, the introduced swaying remains.
-
[REPORTED]/[MERGED] Roll Oscillation w/ AP Alt Hold - 1.5.6.3690.269
EasyEB replied to Scotch75's topic in Bugs and Problems
The Auto Pilot bug seems to be fixed in 1.5, but I still think the plane feels sluggish, like the center of gravity is way to far back. There seems to be more swaying after executing a sharp maneuver. -
Yes, that would be great. I have no idea how that could be accomplished though! In other news: Update 1.3.6 -Ground units now report when they have target in line of sight. -Ground units now report if they move, and in what direction. -Target intel reports if the target is moving, and in what direction. -Other small bug fixes.
-
[REPORTED]/[MERGED] Roll Oscillation w/ AP Alt Hold - 1.5.6.3690.269
EasyEB replied to Scotch75's topic in Bugs and Problems
They never do that ;) -
[REPORTED]/[MERGED] Roll Oscillation w/ AP Alt Hold - 1.5.6.3690.269
EasyEB replied to Scotch75's topic in Bugs and Problems
Patience, children. They never update 1.5 and 2.0 at the same time. -
Greetings! Is it possible to edit some lua somewhere to make the TGP go on station 3 or 9? If so, how? Thanks!
-
Eventhandlers is the way to go.
-
[REPORTED]/[MERGED] Roll Oscillation w/ AP Alt Hold - 1.5.6.3690.269
EasyEB replied to Scotch75's topic in Bugs and Problems
Point 1 is a bug introduced recently. -
Smoke/Fire? Trying to make Huey firefighting mission.
EasyEB replied to Forest Rat's topic in Mission Editor
Having the firefighting helicopters just stop the trigger loop sounds good to me, for whatever that's worth. Forest fires tend to smoke for alot longer than five minutes after the actual fire stops irl :) -
Don't know, this is the first I'm seeing of it. Hey, thanks man! I appreciate it and everything! I think the reason is that for randomization to work in DCS you have to go pretty deep into scripting. The editor is nice for making static missions, not so much for randomized. Yeah, hitting moving vehicles with GBUs are in general not as easy as the pamphlet says :) As you have probably noticed, you can see when you are in laser track mode the spot jumps to the target, and doesn't follow in a smooth motion. This is because of how CTLD works (the sript handeling the laser). I probably could change the update frequency, but I don't know what kind of system impact it would have. I think Ciribob settled on a second (or whatever it is now) for a reason. Try manual lasing when hitting moving targets is the best solution for now. Aw, thats not good at all! What version are you running? Is it at any particular time the menus get duplicated, or any specific menus? There was a problem I noticed a couple of versions back that caused problems if stuff happened between giving a Kursha flight the Scramble command and it actually taking off. That has been fixed though. If you can, please give me as much info as possible as to when this problem occurs, and make sure you are playing on the latest version of the mission. I don't know what may be causing it. Yeah, that is in the nature of the mission I suppose. I figured I'd put in as many tools as possible to get the job done (killing the enemy group) in a combined arms type operation (the concept of working togeather, not the DCS module). You could say the ground units are not required to finish the job, but in another way the air support is not required, and in another way the player is not required. This is because I wanted to give the player the option to orchestrate the assault is a way he/she prefers. When I play it, I rarely engage targets myself, but instead order the air units to strike the heavy targets, and the ground units to mop up. But to each their own. I kind of leave it up to you to role play the feedback, and will not implement it gameplay wise. But I do agree on it, despite randomized forces, randomized locations, randomized support it can get a little repetitive. I mean, it does follow a recipe. So what I can say is this: I know. I'm looking into it. But do not expect thematic briefings on why we must take out the terrorist Boris before John and Jack in their Stryker gets pinned down, and no treats for a job well done :) Also... Update 1.3.2 -A little debug message was left behind, that has now been removed...
-
Hey thanks alot man, I appreciate it! Also... Update 1.3.1 -Kursha flights loadouts changed. The Kh-29 was causing errors making the planes ignore the attack orders. So, until I figure out a solution for that they start with either fuel tanks and two S-25L, or two S-25L and two Kh-25. -Further bug fixes with ground units advancing. The problem was that once either Alpha or Bravo had been destroyed, on the next task when a new Alpha or Bravo has started,they would advance to the target but not update the waypoint if the target moved.Now I think I've finally sorted it so that they countinually move and follow the target. Sorry for any inconveniances that was caused by this.
-
I'm an avionics guy. I only fly the A-10C. I love everything sensors and would take an MQ-9 Reaper module with a well made IR implementation over anyhing older than fourth gen fighters. FLIR, IR pointers, NVGs, laser guided munitions, GPS, datalinks. Oh my. :)
-
Hotfix - Operation Titan Angel 1.2.8.1 -Kursha 1 ammo count bug fixed.
-
Update - Operation Titan Angel 1.2.8 -Both Cursha flights can now start with option of extra fuel or extra missiles. Extra fuel means two missiles + external tanks, extra missiles means four missiles (two of which are the potent Kh-29). Both options have four rocket pods. -Both Cursha flights can now report fuel status. They do not RTB when bingo fuel, so you need to check their fuel status and send them back manually. -Ground units now start closer to the enemy.
-
Update - Operation Titan Angel 1.2.5 -Lots of small bug fixes. -Ground units at last act as intended in regards to advancing and halting. -Gound unit Bravo now consists of Georgian armed forces (BTR-80/BMP-2/T-72B). They use EPLRS just like Alpha, but watch your fire and order them to pop smoke when they are in contact to avoid friendly fire! THEY LOOK JUST LIKE THE ENEMY GUYS! :) -Kursha 1 now has company from Kursha 2, so you now have two Georgian SU-25T to order around. -Kursha flights speed increased when ordered to move to target location. Note that this will also increase their fuel consumption...
-
Trying to walk the line between getting it out as fast as I can and making it as best I can :)
-
Update - Operation Titan Angel 1.1.6 -Bug that caused ground units to continue to advance even though halt command was given/new task started fixed. -SU-25T Kursha 1-1 will now report when its in range for attack.
-
Update - Operation Titan Angel 1.1.4 -There was a bug that made the SU-25T Kursha 1-1 not engage targets at certain places and/or distances. The bug persists, bug Kursha 1-1 now has to be within 25 nautical miles from the target to engage. You can ask Kursha 1-1 how far away he is via the F10 radio. -The SU-25T Kursha 1-1 now carries two Kh-25ML missiles, instead of sixteen Vikhrs. -The SU-25T Kursha 1-1 now fires a quarter of it's remaining missiles every time it does a specific target attack, so the rockets will last a little longer. -The SU-25T Kursha 1-1 can be ordered RTB where it will rearm and refuel and be available for further tasking after 10 minutes on the ground.
-
I think fog of war is enablad, I don't use the F10 map though so I might be wrong. I've got an update coming, I'll see if I can straighten out the map until then.