Scotch75

Hey grimdar, Regarding your first code problem, after you pressed the CODE OSB on the screen, you also need to press the round button on the UFC next to code so a ":" appears next to it. Then you can enter the digits and press ENT. Then STEP and ENT again for each of the bombs. Regarding the AUTO mode, only once you have designated a target, the symbolgy will change on the HUD. You can designate either by the WPDSGN OSB, or use the targeting pod to designate by finding the target in Point Track mode, then using the TDC depress to designate it. The AUTO bombing system needs a point to calculate , to display to you when to pickle. Hope that helps, Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

I wish the cluster munitions for the F-5 could be tweaked as they seem fairly useless with a very small dispersion. Maybe add the MK20 rockeye with better dispersion and effect. Cheers! Sent from my SM-G950F using Tapatalk

Hey no probs mate, glad you got it working. I just ran the mission now as well, I'm getting the same spawn deaths too. I may get time to play around with it tomorrow, will let you know if I get it working. I've got some international cricket to watch lol... [emoji23][emoji967] Cheers! Sent from my SM-G950F using Tapatalk

I'm not sure how much you have edited in the mission editor, but you should not have to download or edit MOOSE at all. It is packaged in the whole mission (.miz is essentially a zip file) by the mission maker. Maybe download again and start from scratch, and you don't need to touch any MOOSE component. Hope that helps. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Yes, the drone was directly over Sirri lasing AAA target. It said "Type 2 in effect, laser 1688, use gbu-12". I was able to use the menu items, "Laser On", the drone replied "Lasing". I went through the work flow of IP Inbound, Spot, In. The drone had a bit of a hiccup here where it would say "Cleared Hot", or "Abort, abort, abort" randomly after a pause. In which case you would have to start the process again. I guess this depends on whether the drone can see you as well. I think the only way to check whether the drone is lasing or not will be with a TGP in laser spot mode with a modern airframe. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Hey Surrexen, Many thanks mate for your continued maintenance of these missions. All appears to work ok, except for one possible glitch. It seems the Predator JTAC may not be lasing even though he says he is via the JTAC menu (type 2 CAS). I was dropping gbu-12s from F-5, checked correct code 1688, but bombs seemingly going dumb. It could be I wasn't quite in the launch envelope, but I pickled in the general direction with good height and speed several times. The bombs did not appear to react at all. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Excellent, in your own time mate. No doubt you are very busy with these latest patches. Yeah, the F-5 is a fantastic module, great fun to fly. Cheers! Sent from my SM-G950F using Tapatalk

Hey Sedlo, Many thanks for the effort you have put in already. Last night I was playing one of your early campaigns, Cordova vs Dreamland for F-5, and noticed triggers etc were not sequential and incorrect in Mission 1. Just wondering if you were going to revisit this one as well? There doesn't seem to be much around for the F-5. Cheers, [emoji1634] Sent from my SM-G950F using Tapatalk

Yes, I think that is what I did IIRC. It is because the Aggressors are considered Red force, and you are at a Blue base, so no ground services available. Hope it helps Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

I also forget sometimes to make sure no A-A weapons are selected as well prior to switching to A-G. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Are you sure you are not still on the carrier d/l which is default on start up? The carrier may not be picking up the bandit to show on the d/l, but AWACS is. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Hey Matt, Yes moving your camera slightly left should help the field of view for the TrackIR. I hold my headset up to the middle of the screen, then slide the camera to be directly in line with the Pro LEDs. That should give a good neutral position. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Or you could be in DF (direction finding) mode on your radio switch. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Try totally disconnecting, then re-taxi to a new catapult and get as close as you can to the shuttle. Reconnect with the "U" key, hopefully it won't rock around as much. Then you should be able to launch. That has worked for me in the past. I think the sim somwtimes gets stuck in that "hooking up" process and animation, so you are not actually attached, even though it looks like it. Hope it helps Cheers! Sent from my SM-G950F using Tapatalk

I think you will need to change the date in the base_mission.miz and camp_init.lua files then run the firstmission.bat file to re-initialise everything. Hopefully that will start at the date at your choice, and keep it going forward into the *_ongoing.miz. @MBot shall be able to confirm if this is correct. Cheers! Sent from my SM-G950F using Tapatalk

I have had this jigsaw for over 30 years. My daughter and I decided to put it together, we finished it yesterday. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

OCD or not, they look absolutely superb mate. Well done, I can't wait to see them in your campaign. Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

Stunning mate, well done Cheers! [emoji1634] Sent from my SM-G950F using Tapatalk

^^^^ exactly. Yeah, the DCS campaign interface and tracking will be cactus. Sent from my SM-G950F using Tapatalk

Generally after prolonged durations. I can start a mission, exit a few minutes in, no problems. I agree with you regarding possibly memory (or even DCS track) related, maybe too many events etc overflow the DCS debriefing list. The only other apps running are trackir and tacview. I have 32Gb RAM and have set a large page file on the DCS SSD. I was able to watch a complete tacview replay after the last mission, at least confirming tacview wasn't hanging, and DCE scripted a new mission showing persistence. However, as far as DCS is concerned, the mission never occurred, as a restart of DCS was required. Many thanks Sent from my SM-G950F using Tapatalk

Hey Miguel, Many thanks. By disabling frenchpack, do you mean deleting the AI french skins? However, this is happening in Mbot's latest DCE which I believe does not have any French skins etc Cheers! Sent from my SM-G950F using Tapatalk

That seems right, I just changed the DCS to DCS.OpenBeta/etc/... Make sure the correct case is used as your path, and the correct slashes ie "/" or "" is used in the the .lua. Mbot describes it in green text next to the path. I think my end of mission problem comes after some script runs during the mission. If I start a mission, then after a few minutes escape out, DCS ends properly to the DCS debrief screen. Cheers! Sent from my SM-G950F using Tapatalk

Doh! I've got it all working, but now I am getting that random DCS black screen freeze when escaping/ending the mission. The screen never goes to the DCS debrief screen, but the DCE debrief and DOS window pops up in the background. I have to CTRL-ALT-DEL, then end DCS with the W10 Task Manager, then restart. Anyone else getting this problem too? It also happens on PB0_CEFs DCE missions. Cheers! Sent from my SM-G950F using Tapatalk

Regarding the first problem, you need to open the .bat files with a text editor and change the default path to your installation path. Regarding the second problem, I have set the date to after 1994 in the camp_init.lua file, then you will need to run the firstmission.bat file. I haven't had a chance to test this yet. Cheers! Sent from my SM-G950F using Tapatalk

Here is screenshot of the .lua file. Cheers!