Speedbrake

Solved it. Since I had the new combined serial number (DCS World Beta - bonded fine), in Release DCS World I deleted my Ka-50 Black Shark module. When I rebooted the simulation and went to modules it said I could download the module. Following the process, I entered the new combined serial number and as they say in Britain...Bobs your uncle!

Okay, I got pissed and took a leap of faith. Since I had the new combined serial number and it worked on the beta version from the log-in but would not bind on the release version....I deleted the module Ka-50 Black Shark. When I rebooted the simulation and went to modules...it said I could install Black Shark 2. Which I did, entered the new serial number when ask and all is well again in simulation land!

BS2 Serial No. Not Binding in DCS World I got the new serial number (BS1 & upgraded to BS2 = new serial no.) from the link under sticky BS2 forum and it worked fine for the beta version of DCS World, however it will not bind for the release version of DCS World. Under modules it does not show a space for serial number. Every time I start release DCS World it says my upgraded serial number is not good. I then enter my new combined serial number and it still does not allow me to fly the simulation...I only get the F10 map - not cockpit in existing mission or instant missions. If I delete the BS2 module...upon reboot of the simulation will it a tell me I am good to install the new BS2? Need someone from the company to answer this - not just a guess.

I purchased BS1 and upgraded to BS2 when it was released. I have used the link to get the new serial number for the now combined BS series. I have updated the serial number in 2.5.6 beta and it is fine. However the new serial number WILL NOT bind in the release version DCS World. I have tried with and without dashes. I have tried turning the module off, rebooting, turning it on. The module list des not show a serial number for BS2. I have checked and double checked the serial number under my profile and am entering the correct number. Suggestions?

Solution: If you have McAfee virus software, it is looking at the 2.5.6 DCS.exe as a virus and has put it into quarantine. Go into the McAfee control page, then to setting. Click on quarantine and reinstate the DCS.exe. Then go into Real-Time Scanning and add DCS.exe as trustworthy. I also found that the 2.5.6 beta doesn't like Black Shark 2 if you upgraded from the first Black Shark. Here you go into the Black Shark 2 forum and look for the sticky on getting a new serial number for BS1 and BS2.

Very handy....thanks!

Charlie means "yes" or "affirmative". It comes from the old days of flag signals. A typical landing operation begins with a "Signal Charlie". The carrier would turn to a heading that would provide about a 10-degree crosswind from the port which would put the wind direction closer to being head-on for the landing deck angle which is 12-degrees off (port of) the carrier heading.

Log errors....for the ships, there was no log error. They appear in the sim underwater. The only thing visible is a wake much like a submarine periscope.

Yes, Markindel's various ship models no longer work!

Not much to see in a picture. They look like a water wake much like a submarine periscope....without the periscope. The ships were fine in the beta program that last time I flew the mission. It is the USS Arleigh Burke Class mod ships that are affected. Just checked the release version....same problem. Therefore whatever changed happened a few updates ago.

Anyone notice that the mod ships like the Cole and Bainbridge are showing up underwater in the latest beta patch? It may have been a patch or two before...I just noticed. Is that any fix out there?

nobody else seeing this???

In the 2.5.5 beta I've noticed that ATC no longer uses your selected callsign, such as Uzi, Ford, etc. but instead uses a number like 4-1-1 or 1-1-1. Think there is a bug in the mix!

I fixed the problem...don't know what caused it but I fixed it by copying over the F-5E-3 input file from the release version to the beta version. It was working fine in the release version. Now all is good in the beta too!

Fixed It Don't know what caused it but after posting the above message it dawned on me that if it worked in the release version....why not copy over the F-5E-3 input file from that version to the beta. I did and it worked!

F-5E-3 sim setup: both the last and current beta update. On the controls setting screen, elevator trim pitch up and pitch down have a slight pink background (different from all other controls on the list) and do not function on my Warthog HOTAS control stick. I've reprogrammed the stick several times to no effect. The release version is fine - stick control and trim works and background on the control page matches all others on the list.

Anyone else having a problem with nose up/down pitch trim? I have the most current beta update (also had this problem on the last update). The simulation doesn't seem to register my stick trim commands. I've reset them a couple of times. In this latest update on the controls setup screen the nose up and nose down pitch command seems to have a light pink background??? My stick trim works fine in other modules. Warthog HOTAS

Wrong Date Oops, last post message should have been 6-10-19.

F-5E Startup Crash 5-10-19 Version 5.5.5 (beta). Started with the F-5E went into sim. As soon as I tried the comms menu to get power connected. F8 was fine, requested hook up electrical but the sim crashed when I selected F2 to turn on, Crashed twice in a row.

Anyone figure out WHY the APU mod freezes the open beta? I'm not a programmer but I've noticed in the lua file that on the old version (not the beta) the mod was set for the "civilian" static object. This isn't a category in the new update. There is another mod "gpu mode" that was set to the "fortification" static object category. This category also is not in the new update. Maybe someone with more knowledge of lua files could look into this. The reason I ask is because I have several missions I prepared that require this mod and they won't start because of it or because I've removed the mod in the tech folder. My option is to go back to the old version and edit the APU out of the missions, then copy them over to the beta.

Anyone figure out WHY the APU mod freezes the open beta? I'm not a programmer but I've noticed in the lua file that on the old version (not the beta) the mod was set for the "civilian" static object. This isn't a category in the new update. There is another mod "gpu mode" that was set to the "fortification" static object category. This category also is not in the new update. Maybe someone with more knowledge of lua files could look into this. The reason I ask is because I have several missions I prepared that require this mod and they won't start because of it or because I've removed the mod in the tech folder. My option is to go back to the old version and edit the APU out of the missions, then copy them over to the beta.

A-4E-C start from parking started blowing up on mission start with the previous beta update and STILL DOES with the 2-20-2019 beta update. It worked fine in the same mission (cold start ground mission) prior to the last two beta updates.

After the most current beta patch 2/13/2019, my A-4E-C blows up at the very start of the mission, just after the start screen. I went into mission editor and removed all weapons and it still blows up!!! Not sure what the problem as before the patch I've flown the mission several times. Anyone experiencing this after patching? No problem if I go to a mission with the F/A-18C.

If you are using a drone...is it being shot down before you contact? Are you using a JTAC that can laser? If your JTAC is in enemy contact, is it being destroyed, try setting "invisible and or immortal" in the advanced settings. If all else fails, download a user posted JTAC mission and look over their setup in the mission editor. Not sure all the GBU laser capability is available in the release version, it works in the beta fine.

DUH!!!!! I feel stupid....I had transposed the code it should have been 1688 not 1866. When I entered the correct code...it took it correctly. I was entering the code on the runway...not when I contacted JFAC.