JeffreyC

Even though posted yesterday, that video is already outdated. It doesn't work like shown there any longer. I had the same problem and posted a bug report for it. Now it seems you have to long press SSS forward long for the seeker screen to show again. Extremely confusing and not well documented at all. I think it will be best of Razbam or one of the groups does a youtube video on the new procedure.

There was a new bug introduced in the newest update causing E2/L to no longer work

Even better the fix was in today's update

No, the UI has to be proper for the user. First off we are not flying only one plane. That itself would be very bad for ED's business model if every user purchased only one module. Second the pilot does lot load out the aircraft. Come one, your post made no sense at all. There is no reason for a person to look up from outside sources for every weapon on every aircraft they are using at home for entertainment.

For the HARMs, I think they either should be not mountable on 4 and 6 as we are not running logistic missions to move weapons around or at the very least a clear indication when mounting them that they are not usable. I have no issue at all with restrictions based on what the aircraft is capable of, and in fact favor this. I do have an issue with the UI causing confusion to users as it is not reasonable for a user to have to reference outside game resources for every weapon being loaded on any given aircraft on the chance that DCS will allow unusable weapons to be loaded.

Yep, for some crazy reason they are now allowing unusable weapons to be mounted on hard-points to completely confuse everything. You have hit exactly the problem I thought there would be as a result. ED needs to either remove mounting AGM-88 on these points or allow them to be launched from them.

Same as in this?

They really should have removed the mounting on those points instead of just restricting launching. For the first time we now have weapons that can be loaded but not used and there is nothing to indicate this in the mission editor/planner or rearming screen. This will surely be VERY confusing and lead to some very unpleasant surprises during missions.

This is very good news! I do scenarios through different time periods so such flexibility is perfect. This decision has restored my faith in looking forward on the F-15E

I think you quoted the wrong person. I specifically stated SP, not MP. I don't ever even go into MP nor any interested in MP. I said in SP, the F10 map shows ejected pilot location.

They show on the map in SP too not just on MP.

Having the same thing I thought I did something wrong or had a corrupt file

Or for any of the other broken ILS on the map for that matter

Even some that seem to work, only work partly. For example Al Dhafra AFB runway 13 the localize is reversed and glide-scope doesn't work.

I think when they updated the INS system to support AINS with GPS available a but was introduced when doing the coding for it. It happens with all weapons that support CCIP and CCRP as well as the uncage target slewing on the Walleye. In all cases it only seems to happen with cold start and no GPS. All had seemed to work fine prior to that update, so think it's a case of adding a new feature also created new bugs. Your CCIP will show any time you have A/G mode on and a bomb in CCIP mode no matter where you are, which help for making testing short

Provided in another bug report on this issue but here is one here also for CCIP. CCRP it takes the target being in the completely wrong place, when it registers at all and not just flips the lineup from one side of the hud to the other. CCIPWrong.trk

As your own statement showed, it does not help at all when there is no GPS. Even if that is a work around when GPS is available, it is without a doubt a bug.

CCIP is independent of any target. CCRP is the one based on a designated target.

Naturally when planning to save I can't line up with the cat and look like a dork driving around the deck But at least was able to reproduce the issue and showed both proper INS alignment prior to takeoff and doing an IFA after takeoff did not correct the problem, so a success in achieving the goal CCIPWrong.trk

I'm having the exact same issue even worse in fact and found it only seems to happen, at last for me, with a cold start. Hot start works fine. Even doing an IFA does not fix it and leaving if in IFA is useless if in a non-GPS scenario. I'll run a mission today and save the track with Bignewy's instructions. Screen shot in the meantime, track to follow.

Have had the same problem as well. No idea why it's marked "correct as-is" especially without any explanation from ED. It doesn't make sense the system can't figure out which way is down so drastically especially when the waypoints course for the aircraft track without issue at the same time. Tried it again and same problem and IFA did not fix the problem. Took screen caps, size limit only let me put one so showing alignment good and CCIP is almost 90 degrees off. This can't be correct. This only happens with cold start. A hot start on the CV does not have this problem.

Looks like latest updates to the F-18 broke support for it. Load DCS lua generates error "Unhandled exception has occured in your application...Length cannot be less than zero. Parameter name: length". F-16 still works without error. Details on error: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ArgumentOutOfRangeException: Length cannot be less than zero. Parameter name: length at System.String.Substring(Int32 startIndex, Int32 length) at DCSF18ALE47Programmer.Form1.loadLua_F18C() at DCSF18ALE47Programmer.Form1.loadCmsFromDcs() at DCSF18ALE47Programmer.Form1.button_loadCM_DCS_Click(Object sender, EventArgs e) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- DCSF18ALE47Programmer Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///E:/SteamLibrary/SteamApps/common/DCSWorld/BACKUP/DCS-CMS-Editor%20by%20Bailey%20v4.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4270.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4300.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.

Maverick locks are very bugged right now. You're getting stuck on in the handoff without it completing. Workaround is to use the H, target what you want to shoot with the pod with the Maverick slaved (pre mode) then use area lock on the Maverick. This will allow it to lock on the location bypassing the locking bugs, and the area will be the target thanks to slaving to the pod. Note this will only work if the target is stationary, it will not work with moving targets.

It is supposed to give longer ranger targeting but currently targeting of mavs are bugged. So it probably will work that way when it goes to stable release :)