Jump to content

okopanja

Members
 View Profile  See their activity

  • Posts

    1953

  • Joined

  • Last visited

 Content Type 

Everything posted by okopanja

  1. okopanja
    You are correct in terms of end effect, but from pure technical point of view, this should not be called loft, and besides will usually work only in certain scenarios. Before the change that roughly coincided with HOJ fix, ER had been a guidance law which I would describe as used a simplified proportional navigation with range dependent proportional factors. After this change it appears the missile is actually using PID controller (proportional, integration, derivation factor). The guidance law defines the desired trajectory as a function. In case of the R-27 this is a straight line between missile and target. In case of AMRAAM/SD-10, depending on range this is either ballistic trajectory or direct line. What happens next is that PID controller measures the deviation from expected trajectory which is used to apply the correction based on P-I-D factors. Since R-27 originally had only P component(s), the end result was that any attempt at faking loft would result to immediate rapid correction and therefore rapid energy loss with no benefit. So back then we had to make sure we actually to but the dot into the circle. However, by selecting I and D component you can control how quickly the missile returns to the desired path and this is how lofting effect was produced with R-27ETER. It is worth to note that ET still uses the old system. so no lofting is recommended here. Here is not too much technical explanation:
  2. okopanja
    Yes, thank you @Flappieand developers...
  3. okopanja
    I played yesterday single session GS and it worked normally. Need one or more time to be absolutely sure. I did not realize how much this issue made things more difficult. Basically I was constantly switching radar ranges(and using radar on HUD), so I get briefly somewhat correct situation. Yesterday it was so easy. Meanwhile NAV glitches are more often(all airports are gone), but I will try to study that closer and file new issue.
  4. okopanja
    This change was introduced 2 patch versions ago. The reason behind the change is that SU-27SK manual (exported version later known as J-11A), explicitly states that if the lock is lost the missile is lost. This could be a limitation of the export version, but at the moment there is no better document source. If you are flying redfor aircraft, it is highly recommended to learn more about radar and sensors and missiles in general. This way you would learn to utilize what you have while understanding the capabilities and limitations of both your own and opponent's weaponry. In addition: altitude and speed have high impact on missile range. Find out what MAR (minimal abort range), notch, and crank are. Practice firing at AI equipped with superior weapons to find out how far you can go without getting hit. I am pretty sure you will then increase your odds against blue, since average blue player simply puts faith into the electronics to do the work for them. Against competent blue player you will have to think hard when to engage and when to run, while at same time exceeding his skills in order to win. China in game has PL-12 and SD-10, it would be interesting to see if the first one will be provided to J-11A. It would be a bold move on ED side (would cause lots of complaints from blue) but not unrealistic since these missiles were pictured on J-11As. The R-77 is actually under-performing at medium to high altitudes in supersonic range. Under these condition fins should perform the best. The modeled drag is to high so these missile have really modest range in game. We hope that future remodeling will fix this issue. However this missile remains to be one of the deadliest at close range and many people use it in this way.
  5. okopanja
    There are parameters... Wait this needs to be tuned...
  6. okopanja
    Works nicely, although missile can not re-lock, but shows up as either 12 or 10 depending on what was mounted.
  7. okopanja
    Well I did not suggest that, I just pointed out what this API likely consist of. The original posted asks us if the new API should be applied, so naturally it would be good to know what was implemented so far?
  8. okopanja
    There exist on the market a product that court more to the players desires, however I would not call it realistic. I may agree or disagree with some development choice, but this module belongs to the better supported modules. For those $80 bucks, you are getting more than any other choice outside from DCS, and when we talk about professional simulators, their prices outpace the DCS modules by several magnitudes. As for the pilots just like any of us they also suffer from bias and memory tends to be a fragile thing. Just to illustrate: what would happen if you were to drive the car you drove 5 years ago? Would the feeling still be familiar to you or not? Would you be able to accelerate and break with confidence instantly or not? On the other side charts provided that their a genuine and made without introducing measurement errors remain as solid proof. So find yourself a chart and try to replicate that performance. Demonstrate the deviation.
  9. okopanja
    Best thing, that daddy f-16 pilot from the video appears to have problems figuring the optimal maneuvering toward target, but junior is respectful which counts as a plus.
  10. okopanja
    It would be interesting to know the total feature sets of both API models. Later likely covers more details in following areas: - engine modeling (e.g. mono-dual-multi-pulse) - own RCS and electronic sigunature - aerodynamic modeling - behavior of controlling surfaces - sensor gimbals limits - sensors - countermeasure effects - interaction with other information sources (e.g. DL) - guidance logic (e.g. loft vs direct) - positioning method Second thing would be to map the specific missile to both feature sets and specific features toconfirm if new new one provides distinct benefits. We know that they both likely have PID controllers. New API has Kalman filters which probably results in refined PID factors + missile is less sensitive to notch if the target keeps flying the same way (not necessarily on linear trajectory).
  11. okopanja
    Working on something that we've all missed in DCS: elevation profile of the route.
  12. okopanja
    The track was generated from ME which, where I started mission in server mode. I wiped out older tracks. I would need to replay it. Do you want me to do it from single player mode? It happens even without radar on, and I think even with EO detect/tracking modes. I will try to reproduce it again. Today I am kind of "booked" with obligations, so perhaps near evening In addition the the airports in navigation modes are occasionally not displayed at all. This is rare, I have seen it twice so far: once after fight with lots of tracks where I had main symptom first. Second 2 days ago when I just joined the server and started taxing for a runway.
  13. okopanja
    SharkPlanner v1.1.0: selection of waypoint/fixpoint/targetpoint moves the map What's Changed Added features: Selection of waypoint/fixpoint/targetpoint focuses crosshair on map location Bugs: When switching maps the coordinates of map local coordinate systems were not recalculated User can not open load or save dialogs. Checkbox present on dialog did cause the SharkPlanner to fail to show dialog if the check mark was set to false. In addition, all keyboard inputs were left in disabled state. Many tanks to @Dustofffor reporting and effort in troubleshooting the issue. Full Changelog: v1.0.2...v1.1.0
  14. okopanja
    it happens on ST as well after first attempt to fix DL. You probably just like me fly MT all the time. Yes competition appears not to be affected. The worst is that even with your own radar the locked target wanders around and you are not sure where he is until you watch in HUD (which still works).
  15. okopanja
    Please attach the dcs.log as well. I suspect that after clicking save the error occurred. It should be shown in dcs.log.
  16. okopanja
    @uboatswould it be technically possible to evaluate effectivness of pl-12 on new API at least in SP?
  17. okopanja
    No change with latest release...
  18. okopanja
    Actually this would be a wonderful opportunity, since SD-10 is otherwise known as PL-12. This would allow to arm J-11As with them as well.
  19. okopanja
    Shark Planner v1.0.2 - this upgrade is mandatory for any map having coordinates in Western/Southern hemispere What's Changed Fixed problem with coordinates display Correct conversion of geographical coordinates in western/southern hemisphere Fixed issue with wrong coordinate being entered in Western/Southern hemispheres into PVI-800. Known issues When switching maps the coordinates of map's local coordinate systems are not recalculated https://github.com/okopanja/SharkPlanner/issues/44
  20. okopanja
    I think I found the solution for the problem, lat/long coordinate remain compatible irrespective of the map being used. However, this uncovered another issue: if you enter coordinates on one MAP and move to another, the SharkPlanner will enter coordinates from prior map incorrectly. I will have to make further changes to the code so X/Z get recalculated based on when user changes map.
  21. okopanja
    No, it can not. This actually makes SHKVAL slewing based on navigation target point unreliable. If the altitude is e.g. 500m then the Shkval will be slewed to 0m. This results that view will show area which is much nearer than the actual area of interest. See here for more details. I kind of did rise issue about this but not officially.
  22. okopanja
    Thank you for reporting. This should be fairly easy to fix. Likely it does not work for Southern hemisphere as well. I have created a bug report here: https://github.com/okopanja/SharkPlanner/issues/40 in case you use github.com. I will fix this in the next release. Btw: I entered the coordinates once on Caucasus, only later to enter same coordinates in Syria. It looked fine, which probably means that maps share the same coordinate system with center located on Crimea. Later edit: just found out the X/Z coordinate systems are separate per each maps. This means I will have to actually use the Longitude/Latitude and derive X/Z from them. Mental note: looks like it's about the time to start thinking on the unit test concept and quality gates implemented in github actions.
  23. okopanja
    Shark Planner v1.0.1: What's Changed Improved position table: Geographical coordinates are showed in single cell in 2 lines Altitude cell displays delta altitude and altitude Introduced distance between waypoints in 2 lines: delta between waypoints / cumulative distance including waypoint Logging improvements Fixed logging levels Logging is removed from dcs.log as much as possible Developer only feature Implement experimental button Button executes experiment.lua which is reloaded on each invocation. Context is provided to store intermediate states. Known issues https://github.com/okopanja/SharkPlanner/issues/40 Direct download
  24. okopanja
    I am glad you liked it. At the moment the focus is on Black Shark, but I will soon start learning Gazelle. The feature list for ABRIS is still not complete, e.g. missing are: targets (except for those coming from Rubikon) waypoint altitudes waypoint names (I might be able to derive this from nearest toponyms. So far it looks like towns are easy pick, but other types of toponyms like mountain peaks and rivers are not that easily accessible. wind information Since the entry is done through dials, it is very difficult to have 100% stable and reliable entry, so I will have to yet to asses which of these are actually feasible to implement. E.g. using the dial for menu navigation and waypoint name entry, looks very finicky and non deterministic when entered properly. I think adding targets into ABRIS might be feasible since it is pretty much the same input method as for waypoints.
  25. okopanja
    Looks like not only DL is affected, but also the NAV mode. (this occured to me only once, but prior to that I had combination of DL problem with radar locks showing bogus entries. Happened on GS, sadly TRK is too large (90MB).
×
×
  • Create New...