71st_AH Rob

Yes, since the last DCS update there has been a persistent bug causing chaos, it was causing the mission crash randomly and the logs were no help. I have finally tracked it down to the AI script that launched the CAP and Intercept flights for both sides so the mission is now up but not totally fixed. I am looking at an alternative that I should have ready in about a week if it works. Hoping for a large turnout on 15 Jan to stress test it if it works.

I have been troubleshooting this problem for a while now, I was running 4.3.73 when the problem appeared, I have been disabling scripts one at a time and updated MIST thinking it was the problem, the only thing in common is running GCICAP. There is no rhyme or reason to when the mission seems to crash but it always does when the script is enabled, sometimes on start-up, sometimes after several hours

Do you have a team website yet? I was thinking of trying to get together a Virtual GH squadron but not enough time. I am running the Virtual RCAF Chatham though and the GH sister organization 1 (F) OTU http://1-fighter-otu.enjin.com/home would like to fly with you guys sometime we should talk about cooperation Cheers Rob

Even better! Three fields would also work better for the Luftwaffe but you need to add all the strange characters as well.

This would fix another issue, currently forces are charging blindly at the objective, in reality they would alternatively move and take up a defensive position while covering other units while they move. A simple abstraction could be to divide the 'force' into thirds with only one third moving at a time. In reality we call this movement overwatch or fire and movement and the distance that a unit moves before stopping is one tactical bound. There is no set distance but they move from one good position to another. For the purpose of this though if you limited bounds to 1km it would be fine for simulated movement of armored forces.

I was wondering the same thing. This worked in the past for me but I'm unsure what the culprit is. Opened 10307 both UDP and TCP forwarded to my server Set the port in the server setup page in DCS Made sure it was allowed through the Windows firewall Server was not visible in the server list and direct connection led to timeout by clients who had connected in the past. Turn off Windows firewall and router firewall and still not working but I noticed I had to change port again... I will look at serverSettings.lua and try again when I get home in a couple of days. I'm not sure what changed, last time I did this successfully was in the spring, there have been several updates since then and ominously I had to upgrade to Windows 10. I have been suspecting it was the Windows upgrade that caused the issue. Since the update to Windows 10 I have not been able to see my server on the master server list from within my network, however everyone else can. I can connect by direct connection to my server internal ip only. Not sure if this is related.

Either this or for all aircraft two fields: One for serial number and One for squadron code. This could work for all a/c from the 109 to the Sabre to modern fighters with some airforces. If the squadron code is not required for a particular a/c it could be left blank and would not show up.

I find I can control the Sabre up to about Mach 1.1 with great difficulty, beyond that it I have not been able to keep the speed up. It definitely becomes a handful over .95 and I do not believe it should having talked to my father about it. They routinely preformed at air displays before big crowds and one of the highlights was demonstrating breaking the sound barrier above the crown. It appears that they were able to maximize the effect of the sonic boom for the crowd by diving straight at it, something that would never be permitted if control were so difficult to maintain. Most documentation I have found states that there is a heaviness or sluggishness at high indicated a/s and low alt and at high and medium alt and above Mach .95 there is a slight tendency to wing roll, nothing like the random oscillations that occur in the sim. See T.O. 1 F86-1 Section VI Flight Characteristics, particularly the subsections on Aileron Control, High Speed and Wing Roll. This section may support your quoted source above, but refers to individual a/c not necessarily new vs old and states that there was a fix for it (I should have another look at T.O. 1-F86-4. I wonder if he was referring to older models to newer, i.e. the F-86A vs F-86F? There was a substantial performance improvement between them. The other observation about speed seems to be true at all alt and configurations for the Sabre, it needs to be in a shallow dive to achieve historic figures for level flight. I should make a chart some day when I have time and compare to the official documentation.

That may be buried in one of the .lua files from ED as I have not found it in the Belsimtek folders. It may ne more then just modifying the Initial Velocity, the Ballistic Coefficient may be wrong, as well.

Magneto Bug Magneto 1 & 2 - on and off positions are reversed in control set up. i.e. Magneto 1 Off corresponds to the on position in cockpit.

A working knowledge of Physics is a bonus, High School Calculus is, however a requirement. So TO 1F-86F-1 states that the Boresight angle should be 0 degrees, the specifications state that it could be elevated or depressed for harmonization up to 1/4 degree. I have checked the F86.lua file and it appears to be set to 0 degrees. I assume that is from the fuselage reference line. To level the aircraft, T.O. 1F-86F-2 para 1-6 has it raised on jack stands so all wheels are 2" above ground. I assume that the primary reason for this is to take the tire out of the equation. This we can not do in DCS, or at least I can think of no way to do it but I feel that the fuselage reference line must be fairly close to horizontal and the error introduced would not be significant for this test which is only to determine that there is or is not an error, not the precise magnitude of the error. T.O. 1F-86F-2 includes information on gun harmonization in Sect IX including FIGURE 9-4 with the various relative dimensions and 9-5 with a graph that indicated bullet drop. The Sabre was armed with the M20 API-T and M8 API ammunition, both with an Initial Velocity of 2910 fps. I have verified that this is the ammo listed in the F86.lua file. The height of the middle pair of guns is ~6' above ground with the landing gear extended. The formulas for calculating the bullet trajectory can be found in AAF Manual 200-1 Fighter Gun Harmonization Section F has a table for the older M2 ammunition with an Initial Velocity of 2700 fps which is close. The table indicates about 520 yds to drop 72" To test, in mission editor place Sabre on threshold of runway at Batumi or other coastal airfield near Sea Level, measure using the measuring tool in the editor every 100 yds in front of the Saber and place an object along the side of the runway to mark that spot. Set the weather to a Standard Day, no wind, no turbulence. From an outside view (F2) fire the guns and observe the mean area of impact. I will bet it will be closer to the a/c than expected. let me know your observations and any hypothesis to explain the variance from your expected result.

Tom, I agree with your assessment of how the gunsight works, it is how I interpret TO 1F-86F-1 as well. I think that the sight is working as expected in RADAR ranging mode, not sure about manual. If it is moving the reticle when changing the manual wingspan when RADAR is tracking a target there might be a problem. I think the problem with inadequate lead might be related to the ammunition and not the sight. Specifically, I think the muzzle velocity may be too low, or the muzzle position is incorrect. To test my hypothesis I parked on the threshold and fired the middle set of guns down the runway which had veh parked at 50 yd intervals along the side of the runway and in exterior view noted where the rounds fell. I would be interested in knowing what other people found when trying this test. I did the math and determined where the rounds should land and they were short. The low muzzle velocity compounded by a lack of trg and practice with the sight is leading to the perception that the sight is faulty and you need to lead the target.

That would be great if someone found out how to do that, but reading the description of it on the web page linked and flying on the server, it loads the METAR data for Sochi at the beginning of each server reset, exactly as your script does. I've seen nothing that appears different from yours.

I think they are using your script like I do.

Glad you are still interested in flying it. There have been no real changes to the mission recently, the influx of updates made forward progress impossible just trying to keep up with testing them to find issues that they introduced. I will look into the AI flights, I have noticed a few times the a/c sitting on the ramp or in shelters, engines running and not moving but I can find no reasonable explanation why. I should have some time this weekend to troubleshoot again. Between, work, sending SHE WHO MUST BE OBEYED off to Paris for six weeks for work and flying in the Storms of War campaign, I have not had a lot of time to chase down this problem. Once Storm of War is on hiatus again, I will try to get a weekly campaign going if there is interest and all is stable. Maybe we will even have some WWII AI ground units to add to the mission by them? Cheers, Rob

Chromium, Does this include the save feature requested by Pikey above? Thanks, I have been patiently waiting for this update.

Thanks, that worked for some reason!

unfortunately, I can not install .NET 4.6.2 I get the following error: Blocking Issues: The setup cannot run in compatibility mode. The .NET Framework 4.6.2 is not supported on this operating system. I have confirmed I am running Win 7 SP1 and the entries in the Registry that are affecting comparability mode are not there. Have asked Microsoft for help but holding out little hope of getting a useful answer. How essential is this update from 4.6.1 to make it work and will it be easy to revert to 1.2.8.1 from 1.2.9.1 if it does not?

Georgian Spring is still up, running Simple Radio server as well now with line of site and distance limitations. I will be getting back to making some improvements soon now that changes to 1.5 have slowed down a bit again.

I am not certain about the guns overheating, however I suspect that the main issue is actually the M3 muzzle velocity. The gun sight may be tracking correctly, however I believe that around the time that Belsimtek correctly changed the guns from the M2 of the P-51 to the more modern M3 that the Sabre was actually equipped with the tragectory of the rounds seemed to have flattened out. The M3 were mounted with an elevation of 0° IRL and prior to the change rounds seemed to arc up from the muzzle then drop to the target hitting the point of aim. After that change the rounds seem to be leaving the muzzle at 0° and dropping, however they seem to drop too fast indicating the muzzle velocity may be too slow. You can test this hypothesis by parking on a runway and firing the guns, measuring where the rounds land and do the math. As for handling, I believe that it handles correctly or at least within a reasonable margin of error clean. The real issue for me is the drag with missile pylons seems excessive, bombed pylons less so. To be clear, the drag from the pylons only, once missiles have been fired is what I am talking about. I have the drag figure for the pylons and all the external stores that the F86-F -35 could be configured with and if I get time, will set up a few tests.

Hold down both push to talk buttons or mapping both radios to the same PTT key.

You need to edit the airfield to the correct coalition. It seems the quick mission generator was intended for air starts.

Are you running Windows 10? I have found that I need to run as administrator or I get to the start button when creating a server in Windows 10 or it Williams ne impossible to click the button.

For some time now the Sabre has had no Comms menu to allow it to contact the JTAC. The Sabre was used extensively as a Fighter Bomber with a FAC and without. Currently we can only simulate without which reduces the usefulness and realism of carrying ordnance in missions. Can we please have the following line added to the comm.lua file for the F-86 in the next patch so we can communicate with the JTAC? utils.verifyChunk(utils.loadfileIn('Scripts/UI/RadioCommandDialogPanel/Config/Common/JTAC.lua', getfenv()))(6) This will add the radio command tree for the JTAC to F6 in lieu of the more normal F4 in most modules which is now used for giving Wingman 4 orders in the Sabre which is quite a good use. I seem to remember that prior to one of the updates before 1.5 that we did have an option in F4 to contact the JTAC.

Are any of you using VIACOM profiles for Voice Attack by Hollywood? I find it much easier than making my own profiles as a starting point. http://forums.eagle.ru/showthread.php?p=2534446