Jump to content

JorgeIII

Members
  • Posts

    321
  • Joined

  • Last visited

Everything posted by JorgeIII

  1. Nickname: Tango -117-; Your profile at ED forum: http://forums.eagle.ru/member.php?u=58218 Chosen plane type: F-86F Country of residence: Argentina Time: GMT-3 Language of communication: English Confirmation of familiarization with regulations of the tournament and the obligation to comply with them: Familiarized with regulations of this tournament, oblige myself to comply with them.
  2. It seems to be a bug with guard channel and radios. In the A-10C in MP we could hear each other only by increasing the volume of UHF radio, even with all radios (FM, UHF and AM) turned OFF. Radio text was RED. We didnt find any way to turn Off guard channel from inside the A-10C cockpit. Turning the intercom switch didnt have any effect on comms either. Great mode, hope we can use it soon.
  3. Thanks Dolphin. You might want to speak directly with Colseg for a concise list of errors and possible solutions. He has done and excellent job. As far as i can tell: Problem with previous version: TM warthog HOTAS has many 2 and 3 position switches. They dindt work all with the oficial release (only worked one of the switch positions as an input). They started working with Colseg mod. The problem might be that for example a 2 positions switch, windows only recognize one off the positions as a button imput. In the game, if the module input is correctly modeled (eg. A10C), the sim detects the two, one if "button is ON" and the other is "button" is off. This doesn't happens with the mig-21. Problem with DCS 1.5: sim inputs work as toggle buttons and they get desynched with switchs positions. DCS 1.5 plus colseg mod bring some of the and 3 position switches back. External lights don't work. Airbreak and emergency afterburner work as a google button.
  4. +1 And yo can add: Lock On number 21: Mig-21 MF Walk Around Mig-21 Fishbed, part 1 and 2. By Hans Heiri Stapfer 4+ Publication Mig-21F/M, by Jaroslav Matoulek et.al.
  5. Still same bug in DCS 1.5. FM radio homing wont work client side in multiplayer.
  6. The bonus sale is welcome but: +1 We should be able to always pay a 100% (or close to 100%) of a Module with Bonus, not only 20% of it. Even so, to pay the 100% of a module with bonus $ is equivalent to only a 20% discount (you have to pay FULL price for 5 modules to get enough bonus $ to cover a 6th module). Specially when there are sales of up to 70% discount. Just an idea.
  7. I also didnt notice any difference in landing configuration with DCS 1.5. It seems your landing with overweight or not looking at your AoA indicator. I suggest you read the manual for the charts, check your weight, speed and Angle of Attack (AoA). Keep your engine running above 60% until touch down for BLC to work. Basically you should be landing with less than 700 L of fuel and no heavy payload. I think 1000 L or 1200L of internal fuel is the max. allowed weight for a clean plane, maybe even less. On final, with a light plane and light wind, you should fly over the inner beacon at around 350 km/h and a AoA of about 8 degrees. Flair at about 280-310 km/h and touch down at 270-300 km/h. As landing speed is not constant and increases with weight, you can use AoA indicator for precise landing. Specially if you are exceeding weight limits. I usually keep about 8 degrees of AoA on final (and 4-8 m/s vertical speed) and use 10-13 degrees AoA for the flair for a smooth touch down at almost 0 vertical speed. If I recall well, the real Mig 21 manual sugest an approach at 4-6 AoA (base) and 7-8 AoA (initial part of final). On final AoA should be increased to 10-13 AoA, which will lower to 9-10 degrees when BLC kicks in, after that you should lower your speed to gain again 10-13 AoA. I find approaching at 10-13 AoA is a little bit to high, but perfectly doable. I don't know if I doing the landing by the book but I prefer to approach at 8-10 AoA. Take notice that AoA indicator might not be working in DCS exactely like in the real plane.(AoA not being steady above 500 km/h IAS, flying level with negative AoA at high speed, etc.) A good way to practice IMO is to make a mission with a Mi-21 with 20% unlimited internal fuel just on final of a long runway like Mineraly Vody. Start approaching at the right speed and flairing a few meters above the runway without touching down and keeping the plane steady on the flair for a while, play a little with AoA, throttle, speed and VS, then fly around and do it again. When you have mastered the flair start doing touch and goes letting the plane touch down very, very slowly without caring where you touch down, just do it very smoothly, you have a very long runway. When you have mastered a smooth touch down at the correct speed start practicing to touch down at a specific part of the runway. After that you can add weight and wind, turbulence and low visibility for a better challenge.
  8. +1. And maybe the ability to take a screenshot of the map that automatically adds to mission briefing pictures.
  9. I think some tools that allows us to write and delete notes, references, marks, flight plans, WP, vectors, targets, etc. in F10 map would be great. Specially if you want to change your flight plan before takeoff. Kneeboard is fine but is only useful if you created the mission or for making your posittion. For reference you can see map tools in games like Silent Hunter and Arma. This written references could be shared with other clients (with and option to share to specific client, group, side or all). In this case a client should be able to filter other clients references on his map. Well, the lack of realism of sharing information in the map might not be a good idea. Maybe it is for FC level. I use a lot F10 for reference and navigation in 3rd party servers and to share info with squad members using radials and distance or coordinates and I like it this way. But I would like the ability to mark and make references on my F-10 map. Hope you like the idea.
  10. Real Mig-21 F time for reaching 20,000 m: 8-10 minutes DCS MIG-21bis (heavier than the F): 5:18 minutes from full stop at the runway to 20 km, at sustained climb (not zoom). As the climb from 0 to 10 km is fine (about one and a half minute), the aprox. 3 to 5 minutes error is in hight altitude performance (between level flight at 11,000 km accelerating to mach 1,9 and the sustained climb to 20 km) I really don't know if I want this bug fixed, I like the idea of outclimbing a FC F-15 in multiplayer ;).
  11. Basically Flight director = keeping trim pressed. We have to adapt as our controllers are not the same of a real KA-50. Those who have a Force Feed back joystick might be closer, I have TM Warthog Hotas. If you want to do fast maneuvers smoothly you can't be constantly pushing and releasing trim button and recentering the joystick or waiting a few centiseconds for gaining control again.(It depends of how you have trim setup in game options). Using flight director you can still trim controls (without setting new autopilot values) while maneuvering, you can't do it if you have to keep trim button pressed. This is specially important if you have same curves in your joystick, as it allows you to keep it in the sweetest point. If you want to master the KA-50 I suggest you master both modes: full autopilot flying (usefull on steady flight and slow maneuvering) and Flight Director mode or "trim pressed mode" (usefull for smooth, fast maneuvers). Autopilot completely OFF is a completely different thing. It turns OFF when you have an hydraulic failure or manually turn OFF autopilot channels. You loose autopilot stabilization, you don't loos stabilization while trimming or using Flight Director. And yes, after mastering the Huey flying the KA-50 is a pice of cake.
  12. Fact: DCS-21 BIS performance at high altitude is excessive. Not a big bug, but an evident one. There is a tendency to over discuss some evident bugs, and sometimes are initially neglected by the devs, but eventually fixed. A few examples are the excessive horizontal acceleration and scripted speed limit bug. Speed limit was fixed but drag near max speed was not. This lead, with the lack of control of AFT thrust at different regimes, to a tendency to overspeed. For a time we had to manually use the nose cone to keep a steady mach speed. Fixed in DCS 1.5. Tacview is not working for me in DCS 1.5, but here you have some basic numbers: Sustained climb at 850-900 km/h TAS from under 1000m at 900km/h to 1000m (its fine): (clean plane) Time: 105 seconds (01:45) Average vertical speed: 85 m/s Climb angle: from 35 (initial) to 15 (10,000m). Starting at max IAS (aprox. 1250 km/h) sustaining 1250 km/h TAS brings a similar number. You can make a SUSTAINED (not zoom) climb to 10,000 m much faster. Sustained Climb from 10,000 m to 20,000 m at mach 1.8-1.9 (its excesive): Time: 58 seconds (00:58 ) Average vertical speed: 172 m/s (almost constant, should be around 125-150 m/s initial and SHOULD be lower at higher altitud) Climb angle: constant 35 degrees There is a nice page with historical mig-21 data, pilot study documents, etc.: http://www.mig-21-online.de Im sharing a hand made chart from this page. "High alttitude program example". Its a climbing profile chart with altitude and climb speed. It has some errors, lack some numbers, dosent state Mig-21 version nor loadout. But as far I can tell numbers go by the manual and basic aerodynamics concepts. Basically you can see that initial climbing vertical speed from 10000 at mach 1.8, 1.9 is 125 m/s (other data indicates 150 m/s) but more important it shows how climbing speed lowers with altitude. Current DCS Mig-21 has a completely different chart, climbing speed dosent lower at all. In the chart would look like a line going straight up until 21,000 m (when engines fails) Other data from this page suggest the MIG can sustain a clim rate of 0.5 m/s at 19,000m, current DCS mig-21 can sustain over 150 m/s at this alttitude.
  13. This, every time I try to host if I set the public option in the server options to ON (shows the server in the list) I get a CTD when I press START. If the server is not public it runs just fine but it wont show up in the list. Clients can join by IP. Same network settings and server settings use to work fine before. More info: This error happens only if the internal PC IP is set to static (for port fowarding). If I set internal IP to auto and DCS server to public the server will launch fine but wont show up on the list and clients cant join by IP cause the port are not correctly fowarded, if that makes sense. Attached system info and DCS log. Specs: I7 2600k @ 4.8 Ghz. 8 GB DDR3 @ 2 KHz SSD GTX 980 X-Fi sound blaster Track IR TM Warthog Hotas Saitek pedals Saitek MFDs. dcs.zip
  14. Golo: take it easy. I can't tell if you are just trolling or you can't read /understand previous posts nor the mig manual and just have a bad attitute. I will answer you only once. Snafu clearly said he was talking about 23 km, not 29. If you are able, try to climb DCS Mig-21bis by the real manual, check you time, angle and vertical speed from ground to 10km and from 10km to 21km. Then come back and tell me im lying. With current FM with excessive performance you just don't have to follow the manual procedure for reaching higher altitudes. We are talking about high altitude performance, about a FM ability no mantintain a 35 degrees nose up sustained climb from 10km to 21km. (sustained = not loosing speed if not clear enough, not zooming, there is not need to zoom right now). The DCS mig can pass through its service ceiling (17.5km), with at least a 25 degree climb while still accelerating, it will reach 21 km while still accelerating in the climb (horizontal and vertical acceleration). Current service ceiling is = engine failure altitude (about 21km). If it wasn't for engine failure at 21 km the mig climbs (sustained climb, again, no need of zoom climbing) as if it service ceiling was near 30 km. I tested climbing to 21km only twice in DCS 1.5, I will do a hard testing this weekend and bring more specific data about hight altitude performance.
  15. Thanks Cobra for answering. As it is right now the Mig will SUSTAIN a climb of at least constant 25-30 degrees from 10000m to 21000m, until engine shuts down. It will climb much faster and with a greater angle from 10k to 21k meters than from ground level to 10k m. Zoom climb from manual: At mach 1.9 and from 15.5 km- 16.0 km altitute (service celing 17.500m for full AFT and two missiles) pull up (up to 2G force max) 10-15 degrees (from initial) and mantain untils IAS is lower than 530 km/h, stop AFT, nose down (0.3-0.4 G), recover. Here I dont know the value for "initial" angle. It should be the steady, sustainble, climb angle, but is not specified, 35 degrres seems too high IMO. A zoom climbing as specified in the manual is not even needed as you can do a sustained climb at a greater angle (35 degrees) and with a heavier loadout. The limit is not engine thrust at high altitut but the scripted engine failure. If you follow real manual instructions for the zoom the mig will just overspeed instead of loosing speed.
  16. This, on the ground, with engine and all systems OFF, before and after flight, Port an starboard suction relief doors move as if they where working. Small bug, easy to reproduce, but in case you need a track or system specs ask for them. The door is the one you see here opened, under the pilot seat, just foward and a little under the wing:
  17. NVidia Card here. Vsync ON in game options, FPS are limited to max refresh rate of my monitor (60 FPS or Hz) and the "microstuttering" is much, much better.
  18. Same thing here. I dont know excatly what it is but when things move fast on the screen, like flying low and using F3 view, or moving your head fast in cockpit, the current 90-120 FPS "feels" momentarily like 20 FPS. It doesent look like tearing, it´s like frames where missing or skipping. Something is not entirely right. Specs: Windows 10. GTX 980, last drivers. 1080p. I7 2600k @ 4.8 GHz. 8 GB DDR3 @ 1,9 KHz SSD Xfi creative sound card TM Hotas Saiteck Pedals and MFDs. TrackIr.
  19. Yeah, test it yesterday and find the same. I loved the power but doesnt look too realistic. Theres is a problem with power / drag over 10,000 meters. Drag seems OK, I would say an excess of power seems to be the cause. Climbing to 10,000 m by the manual at about 900 km/h TAS is ok. You can initially mantain a 35 degree climb angle and slowly lower it to about 15 degrees to keep you TAS till 10,000. You can accelerate to mach 2.0 at this altitute like before but when you pull back to continue climbing while maintaining your mach speed you can keep almost a 35 degree nose up attitude and climb like a rocket (over 100 m/s vertical speed), with no limit, until you engine shuts down at about 21,000 meters (scripted, lack of oxigen?). If you pull up less than 35 degrees, lets say 20 degrees, with the current flight model, the mig will overspeed while climbing. The Mig should be at the edge of flight envelope at arround 17,000. This post should be moved to Flights Dynamics in the Bugs reporting section.
  20. Los servidores para la actualizacion estan temporalmente dados de baja por exeso de trafico. Post 5: http://forums.eagle.ru/showthread.php?p=2501438#post2501438 Mañana estarian los archivos para descarga directa. Slds.
  21. If we have a CTD in single player the track of the mission wont show up in thre track folder (CTD prevent us from saving it). Is there a hiden file that keeps the last single player track? I ask this to help in bug reporting. Thanks.
  22. Thanks. I didnt check VRAM. Not that this mission is so important. I was just flying it to compare FPS as it is a classic low FPS mission. It was reported because the bug is so specific that it should be easy no nail down a CTD bug that may also be the cause of others CTD more difficult to find. Otherwise the KA-50 is working fine, I love the directx 11 smoothness of 80-120 FPS!
  23. Thanks a lot Maverick for your missions and incoming update!
×
×
  • Create New...