JeffreyC

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 :)

Have the problem with handoff hanging at T with D Mavs

I cold start and never use autostart, but that is my preference. To each there own. Nothing is better or worse than anything else.

I do, and I don't have any problem. Hence not understanding. :huh: Guess just have to see when an official response comes from someone at ED for what you seem to be having. :thumbup:

Not sure what people are having a problem with. Use CCRP almost exclusively with the pod for target designation and not having any issues at all. First thought people are confusing the targeting of the F-18 and F-16, where the F-18 you designate a target, but the F-16 what you track is the target without any designation required. I've been loving the changes so it doesn't mess up the steerpoint when targeting.

It DOES say ready and at 10 alignment but the heading is wrong. Hence the bug report. Even with a full standard alignment prior to flight, it does NOT store as stated by Wags for the aircraft not having been moved since last shut down as stated in the link included. Your profile also does not seem you are with ED. As this is a bug report this should be the end of it pending a real response or if you do work for ED then the company does not care about bugs.

Totally disagree. This is contra the very nature of a stored heading and as stated by Wags "You generally use a stored alignment if the aircraft hasn't moved since it was last shut down" As it is, stored is not usable since last shut down, and your method makes stores alignment useless and does not coincide with what is stated as the purpose of a stored alignment.

Though stored INS is stated as being for if the aircraft has not moved since last being aligned that does not work. After landing to rearm and refuel, on starting up again if using the stored INS it loads what was at the very beginning of starting the mission not when the F-16 was shut down especially regarding heading this has been noticed. Normal alignment works properly. To reproduce: Start a mission in the F-16 using any alignment as first time works fine in both ways. Take off then land (or possibly just turn the aircraft), shut down the aircraft (or turn off INS), restart the F-16 and select Stored for INS alignment. Aircraft heading is the original heading at the start of the mission not the heading when the F-16 was shut down. Turn INS off then reset to Normal alignment and heading is the correct present heading of the F-16.

Sadly even here there are some idiots. :( Been using this for months both with my home system and office on workdays. Everyone can contribute and can be scaled down or paused if you do something that needs more power. :)

A max number for mission planning yes, but not for having at the airfield. Additional plans could, and should, be in hangers for later missions so there isn't a requirement to skip a mission while waiting for replacements to arrive when AI eject at bingo :P

Not you. Same problem and see fix is being worked on for the next update :)

Well sadly not for me. Unless there was something other than the steps that come up after running "liberation_main.exe" I have done everything and it is run as administrator just as RC9 was. New UI is great but with not being able to actually fly missions it is offset :( EDIT: Very odd thing, the original save I created will not allow a mission to be flown but creating a new campaign does work. If it happens again I'll try and see if I can find any patter or reason the save would fail. EDIT2: OK some campaign settings cause the failure. Using all default settings as a control test everything worked fine. However, setting up a campaign with USA 1990 vs Libya 2011 force models using the Persian Gulf - Emirates map with a start time of Winter 1985 caused the failure. And yes, I do have the Persian Gulf map :) EDIT3: Further testing it seems it is the Libya 2011 forces selection that is causing the problem. All other settings the same but changing opposing forces from Libya 2011 to Russia 1990 works.

I seem to be having a problem with the new version. The mission file for DCS isn't being created and with I click Fly Now nothing seems to happen whereas RC9 had a screen pop up for starting the mission. I checked the preferences and everything points to the right folders it asks for. Was there an installation step I missed? :(

Great job again! This really adds a lot to the game and your work is amazing and very appreciated! :)

I too like detailed immersion, but at the same time not everyone has or can afford the same controller hardware. This can contribute to the very problem by not giving smooth or precise enough control. Practice is not the only thing to consider. An "easy" function as an option, let me put emphasis on that, OPTION, that can be enabled for those that need it for whatever reason but can be turned off as with others that are present. More of a midpoint between full detailed reality and the unlimited fuel extreme other end.

I love this! it really adds a LOT to DCS! I did nothing a problem though. Using RC9 several times even setting the mission generator to have my flight start cold it starts off in flight. This has happened even with deleting the flight and changing from a CAS to CAP with the same results. It doesn't always happen, so can't pinpoint how to recreate the issue.