skywalker22

Sorry, I did now thats from the same track.

ED, I think what guys are saying here are 100% correct. Just check this image, which means RWR in current version in USELESS! pic: each line represents one moment (f10 map and rwr situation at one point) I was really suspicious about RWR behaviour, specially on Sunday's TACT Persian Gulf mission , I just couldn't get any decent info from RWR, now I know why. Thx guys for all the contribution, I hope ED sees their error. And now I did this simple test of comparison real situation from F10 map, and RWR. And here is the strange result. There is no threat that EVER comes into inner circle. Strange, right? From so close distance that the bandit shots at me. f16_RWR_issue.trk

What are you saying, that lethality level depends solely on the distance? I assume you guys are only doing test against AI, right? You don't even know exactly how are they paint you in which mode (tws, rws, azimuth deg, numnber of bars) and so on. Lethality level depends also on more other things such as the type of radar or other emitter being used by the threat, to determine the level of lethality. Therefore, if two threats are emitting signals at different strengths, but one is using a more lethal type of radar or emitter, the AN/ALR-56M will prioritize the more lethal threat over the other. The point is, there is numberous of things that determine the level of lethality, and its far from being simple.

Man! You are the man. I never actually knew I can drop bombs later (closer to the target) when the max toss anticipation cue ends flashing. Everyone is telling & showing to start pulling up exactly into toss when that cue (circle) ends flashing. Your explanation was perfect! And I also now understand the whole concept. God damn, you saved my day, if not a year Tested, flew straight for 5 more seconds and then went into toss - and you won't believe, bombs went off my wings in my very 1st attempt. Finally one with some correct information. Thanks so much mate, I buy you a beer if we 2 ever meet.

Please try higher angles, you will see how hard, or more close to impossible it is.

At low altitude, does it also work at angles higher then 30deg (40,45, or higher)? Because to me it seem to be closer to mission impossible. @BIGNEWY I would strungly suggest that you try toss by your self, there is definitely something not right, please. ps: if you check my tracks, you can see there is nothing wrong with my technique, if it is, can someone please show/explain how it should be done correctly.

Look at this, it was almost perfect pull-up, and no bomb release. 45deg release angle. Almost mission impossible to release bombs over 30deg. f16_CCRP_toss_bombing5_45deg_NOT_OK_2.trk

I did some more tests, and the whole point is not to pull 4G, but to be at all time of the pull-up on the Horizontal bar (horizontal bar is the indicator of pull-up rate). What I also found out, is setting Release Angle up to 30, makes releasing toss bombs way, way easier (whole process is not as difficult and precise as when using higher angles). I also managed to release bombs at Release Angle of 35, 40 and 45, but its so damn hard, specially keeping the FPM on horizontal bar all the time of pull-up. So now, what can be wrong? If we suppose to have a constant pull-up of 4Gs, there is something wrong with the travel of Horizontal Bar indicator, because if you don't follow it, you will never be able to release bomb(s).

Since last update, CCRP TOSS bombing just doesn't work (again). Issue: flight path marker cannot reach the solution cue to bomb release. Did many different kind of tests (faster, slower G pull-up), but nothing seem to work (and with neither bomb). Note: I start pressing and holding the bomb release button just before going into toss (like Tricker explains it here). PS: I also tried same thing in DTOS mode, and the same result, not dropping bombs. And track files f16_CCRP_toss_bombing1.trk f16_CCRP_toss_bombing2.trk f16_CCRP_toss_bombing3_3_attempts.trkf16_DTOS_bombing4.trk

Correct. AIM-120C in BORE mode only looks straight ahead, so through the center of the HUD (missile diamond symbology).

Indeed insane details. I just hope optimization will be done properly, else we will need state of the art pc

FCR on off, launching AIM-120C-5 missile in BORE mode with a use of JHMCS, currently in DCS does not work either. Not even inside of 120deg (60 on each side from the bore line). Not sure if its a bug, or a work in progress.

Regarding the guidance modes, the basic principles of BORE and SLAVE guidance are the same for the AIM-120C-5, AIM-120C-6 as for the AIM-120D. In BORE mode, the missile uses its own active radar seeker to search for and track the target. In SLAVE mode, the missile can be guided by an external radar, such as the radar on the launching aircraft or a ground-based radar system. Comparing AIM-120C-5 and AIM-9X: in BORE mode, the AIM-120C-5 uses it's active radar seeker to search for and track the target, whereas the AIM-9X uses it's infrared seeker to track the heat signature of the target. While the basic concept of BORE guidance is similar between the two missiles, the underlying guidance technology and operating principles are different. In DCS this works just fine. In case if you not sure how to use it, check it out here: 1. BORE MODE: 2. SLAVE MODE: I think there is an issue here, that it also works in SLAVE mode. With no FCR, AIM-120C-5 in BORE mode should only search and fire with it's seeker head, not in SLAVE. Or am I wrong? 2nd issue, FCR on off, launching AIM-120C-5 missile in BORE mode with a use of JHMCS, currently in DCS does not work either. Not even inside of 120deg (60 on each side from the bore line). Not sure if its a bug, or a work in progress. @BIGNEWY Am I correct?

FOV for the HTS AN/ASQ-213 may vary depending on the specific implementation and configuration of the system. However, according to publicly available information, the HTS has a wide-angle, stabilized sensor system that provides a FOV of approximately 120 degrees in azimuth and elevation.

+ seem like the font is bold, that's why it's so hard to distinguish characters (6 for example, it looks like 8). Personally I would make font thinner (not bold) if possible. It helps turning the brightness down, so characters don't shine that much, but still, because of the bold font it's hard to distinguish some characters.

What do you mean exactly? Can you please elaborate a bit more? thx

I studied about guidance modes of the AMRAAM and also with conjunction with JHMCS a bit more, here it is: In BORE mode, the missile uses its own radar to search for and track the target. The missile is launched and guided towards the general direction of the target, and the missile's onboard radar scans the area to detect the target. Once the target is acquired, the missile's guidance system directs it towards the target. In SLAVE mode, the missile is guided by an external radar system, such as the radar on the launching aircraft or a ground-based radar system. The external radar tracks the target and sends guidance signals to the missile, which adjusts its course accordingly. The main difference between BORE and SLAVE mode is the source of guidance information. In BORE mode, the missile uses its own radar to search for and track the target, while in SLAVE mode, the missile relies on an external radar system to guide it towards the target. BORE mode is more autonomous and can be used in situations where the launching aircraft is not able to provide guidance, while SLAVE mode provides more accurate guidance and can be used in situations where the launching aircraft has a more advanced radar system. When using JHMCS with the AIM-120C missile, there are some differences between the BORE and SLAVE guidance modes. In BORE mode, the missile uses its own radar to search for and track the target. However, when using JHMCS, the pilot can use the helmet-mounted display to cue the missile towards a specific target. The pilot can designate a target by looking at it through the helmet-mounted display, and the missile's guidance system will direct it towards the designated target. In SLAVE mode, the missile is guided by an external radar system, such as the radar on the launching aircraft or a ground-based radar system. When using JHMCS, the pilot can use the helmet-mounted display to cue the missile towards a specific target just like in BORE mode. However, in SLAVE mode, the external radar system provides more accurate guidance signals to the missile, allowing for more precise targeting. The main difference between BORE and SLAVE guidance modes when using JHMCS with the AIM-120C missile is the source of guidance information. In both modes, the pilot can use JHMCS to cue the missile towards a specific target, but in SLAVE mode, the external radar system provides more accurate guidance signals to the missile. The AIM-120C missile's radar has a field of view (FOV) of approximately 60 degrees on either side of the missile's centerline. This means that the radar can scan an area up to 60 degrees to the left or right of the missile's nose. If a target is outside of this 60-degree, the missile may not be able to detect it using its own radar in BORE mode. However, when the pilot is using the JHMCS, the pilot can use the helmet-mounted display to cue the missile towards a specific target, regardless of whether it is within the radar's FOV or not. The pilot can designate the target by looking at it through the helmet-mounted display, and the missile's guidance system will direct it towards the designated target. So, while the AIM-120C missile's radar is limited to a FOV of approximately 60 degrees on either side of the missile's centerline in BORE mode, the use of JHMCS allows the pilot to cue the missile towards targets outside of this range.

I read that thread. That's actually not the same, if I go to Settings or what ever other menu, I do have any issues or crashes. My DCS game crashes, when I want to Close it from the main menu after some time left it idling. I can try to do the same as he did, rename the DCS folder, so the game will recreate new files\folders inside of it. Will let you know. But this way we cannot find the real reason for the crash.

Boresight (BORE) mode: 1. When HMCS (Helmet -Mounted Cueing System) is not powered, the missile seeker looks ahead on the aircraft bore line. This is called a mad dog shot since the missile flies ballistically out to a point without guidance, then turns on its onboard radar and locks up and flies to the first radar contact it finds. It has no IFF (Identify Friend or Foe) system, so it doesn't distinguish between a friendly or a hostile. 2. When HMCS is powered, the seeker is boresighted to the Helmet Mounted Display’s reticle. However, the missile is limited to the restrictions of the FCR’s field of view.

So actually for the boresight mode, FCR is not in use, and you can only look and lock something through the seeker (I called it a radar) on the missile it self, right?

Will check it out tomorrow.

Again, same thing, left the game in main menu, and after some time, wanted to close it, and same thing happened, I had to close it by force. 2023-04-12 18:22:09.262 INFO APP (Main): Screen: MissionEditor 2023-04-12 18:22:12.067 ERROR LUA-TERRAIN (Main): getRunwayHeading: not found runways for './Mods/terrains/Syria/AirfieldsTaxiways/Naqoura.rn4' airdrome 2023-04-12 18:22:12.067 ERROR LUA-TERRAIN (Main): getRunwayHeading: not found runways for './Mods/terrains/Syria/AirfieldsTaxiways/Kharab_Ishk.rn4' airdrome 2023-04-12 18:22:12.067 ERROR LUA-TERRAIN (Main): getRunwayHeading: not found runways for './Mods/terrains/Syria/AirfieldsTaxiways/At_Tanf.rn4' airdrome 2023-04-12 18:22:12.253 INFO APP (Main): Screen: MainMenu 2023-04-12 18:22:13.938 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2023-04-12 20:06:52.378 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1920, 1080] 2023-04-12 20:06:55.627 INFO APP (Main): Screen: Settings 2023-04-12 20:06:57.182 INFO APP (Main): Screen: MainMenu 2023-04-12 20:06:59.086 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2023-04-12 20:07:07.840 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1920, 1080] 2023-04-12 20:07:08.827 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2023-04-12 20:07:08.832 INFO APP (Main): application shutdown 2023-04-12 20:07:09.333 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 0 2023-04-12 20:07:09.336 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 1 2023-04-12 20:07:09.336 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 2 2023-04-12 20:07:09.474 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 3 2023-04-12 20:07:09.592 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 4 2023-04-12 20:07:09.610 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 5 2023-04-12 20:07:09.613 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 6 2023-04-12 20:07:09.617 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 7 2023-04-12 20:07:09.617 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 8 2023-04-12 20:07:09.621 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 9 2023-04-12 20:07:09.621 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 10 2023-04-12 20:07:09.622 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 11 2023-04-12 20:07:09.622 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 12 2023-04-12 20:07:09.623 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 13 2023-04-12 20:07:10.578 INFO TERRAIN (Main): lSystem::exit() 2023-04-12 20:07:10.588 INFO TERRAIN (Main): lSystem::CleanScenes() 2023-04-12 20:07:30.229 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1920, 1080] 2023-04-12 20:07:30.241 WARNING SCENE (11860): Scene was removed with 4 alive objects 2023-04-12 20:07:30.544 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2023-04-12 20:07:30.545 INFO EDCORE (Main): try to write dump information 2023-04-12 20:07:30.552 INFO EDCORE (Main): # -------------- 20230412-200731 -------------- 2023-04-12 20:07:30.553 INFO EDCORE (Main): DCS/2.8.3.38090 (x86_64; MT; Windows NT 10.0.22621) 2023-04-12 20:07:30.554 INFO EDCORE (Main): E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt\Visualizer.dll 2023-04-12 20:07:30.554 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff9b066d80 00:00000000 2023-04-12 20:07:30.555 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'E:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'Mitja Bonca' 2023-04-12 20:07:30.556 INFO EDCORE (Main): OS-Version: 10.0.22621 () 0x100-0x1 2023-04-12 20:07:30.558 INFO EDCORE (Main): 0x0000000000086d80 (Visualizer): MouseCursorManager::clipCursor + 0x0 2023-04-12 20:07:30.559 INFO EDCORE (Main): 0x0000000000007826 (dxgui_win_adapter): gui::ApplicationWin::skipBoxMouseCursor + 0x36 2023-04-12 20:07:30.560 INFO EDCORE (Main): 0x0000000000004424 (dxgui_win_adapter): gui::ApplicationWin::dispatchMessage + 0x74 2023-04-12 20:07:30.560 INFO EDCORE (Main): 0x00000000000034d7 (dxgui_win_adapter): gui::ApplicationWin::~ApplicationWin + 0x6F7 2023-04-12 20:07:30.561 INFO EDCORE (Main): 0x0000000000018231 (USER32): DispatchMessageW + 0x741 2023-04-12 20:07:30.561 INFO EDCORE (Main): 0x0000000000017eec (USER32): DispatchMessageW + 0x3FC 2023-04-12 20:07:30.561 INFO EDCORE (Main): 0x000000000002306d (USER32): GetClassLongW + 0x58D 2023-04-12 20:07:30.561 INFO EDCORE (Main): 0x00000000000a2c94 (ntdll): KiUserCallbackDispatcher + 0x24 2023-04-12 20:07:30.561 INFO EDCORE (Main): 0x00000000000014d4 (win32u): NtUserPeekMessage + 0x14 2023-04-12 20:07:30.562 INFO EDCORE (Main): 0x0000000000021b8f (USER32): PeekMessageW + 0x1CF 2023-04-12 20:07:30.562 INFO EDCORE (Main): 0x0000000000021a5c (USER32): PeekMessageW + 0x9C 2023-04-12 20:07:30.562 INFO EDCORE (Main): 0x0000000000853414 (DCS): SW + 0x3BD064 2023-04-12 20:07:30.562 INFO EDCORE (Main): 0x0000000000105617 (Visualizer): smSceneManager::DestroySceneManager + 0xD7 2023-04-12 20:07:30.562 INFO EDCORE (Main): 0x000000000086e9c5 (DCS): SW + 0x3D8615 2023-04-12 20:07:30.562 INFO EDCORE (Main): 0x00000000023542f7 (DCS): AmdPowerXpressRequestHighPerformance + 0xFB02F3 2023-04-12 20:07:30.562 INFO EDCORE (Main): 0x0000000000c50292 (DCS): SW + 0x7B9EE2 2023-04-12 20:07:30.563 INFO EDCORE (Main): 0x000000000001269d (KERNEL32): BaseThreadInitThunk + 0x1D

Is it the same sluggish feeling for pitch and roll? I have VKB Gunfigjter MkIII Ultimate joystick, with no curves, and all it feels pretty fine and natural to me.

Sorry I don't have a clue. Does it mean that the DCS app shrinked to the size of 0, 0? Maybe when I pressed Close command, it did that? I just checked into the log file which was inside the zip file (where crash and dump files are saved as well), and there is a lot of more stuff. This is the one, search for the our, and what is after is : 17:51:37.643 (there is a lot more info). dcs.20230410-191532.log

As you said, I stopped flying, then left the game in main menu, and doing other stuff on PC. Then after 85min I wanted to close it, and this error occurred. Game didn't even close by it self.