towsim

For demonstration purposes, I installed DCS on a Surface Pro 4 with 8 Gb main memory. The graphics adapter has 4Gb memory. As soon as the sim starts, only black and white is visible outside the cockpit. The only objects visible are white clouds on a totally black background. If a shadow hits an object inside the cockpit it is covered by an opaque, black shadow. Has someone the same problem and solved it probably ?

67 here. Started with VC20 and Blue Max.

Ich habe DCS auf meinem Entwicklungsrechner und auf meinem Testrechner gleichzeitig am Laufen, unter Benutzung eines Accounts. Bei der 1.5… Version habe ich mir eine zweite A10 zulegen müssen um meine Applikationen zu testen. Bei der 2.0… Version konnte ich alle Modelle parallel benutzen. Allerdings habe ich schon lange nicht mehr getestet. Vielleich hat jemand eine ähnliche Konfiguration mit der letzten 2.0… Version ausprobiert?

Im Bild 1 ist die Batterie offensichtlich eingeschaltet und APU Generator und Triebwerksgeneratoren sind aus. In diesem Zustand ist nur das UHF Radio benutzbar. Das soll dem Luftfahrzeugführer bei einem Kaltstart ermöglichen eine Startup Clearance einzuholen. UHF deshalb, weil der westliche, militärische Funkverkehr hauptsächlich über UHF läuft. Auch hier ist Voraussetzung , dass die UHF Box eingeschaltet ist. Die VHF Boxen brauchen mindestens die APU mit eingeschaltetem APU Generator. Vorgehensweise: 1. Am electrical Panel Battery Power On 2. UHF Box linker Drehschalter auf Main 3. UHF Box rechter Drehschalter auf MNL 4. UHF Box Frequenz des lokalen Kontrollturms einstellen Am Intercom Panel 5. Intercom Panel Drehschalter auf VHF stellen 6. Intercom Panel VOLume zeigt nach 12Uhr alle anderen zeigen nach 8 Uhr Das UHF Radio sollte jetzt benutzbar sein. Für die VHF Radios (Battery Power ist bereits ON): 1. Am electrical Panel: Inverter Schalter auf STBY 2. APU einschalten und warten bis die APU Drehzahl 100% erreicht. 3. Am electrical Panel: APU Generator Schalter auf APU GEN PWR stellen. 4. VHF 1 Box: rechter Drehschalter auf TR 5. VHF 1 Box: Linker Drehschalter auf MAN 6. VHF 1 Box: VHF Frequenz des lokalen Kontrollturms einstellen. 7. VHF 2 Box wie VHF 1 Box einstellen. Über VHF 2 kann der Kontrollturm nicht Kontaktiert werden, da dieses Frequenzband nicht von ATC abgedeckt wird. Alle Funkgeräte sollten jetzt normal funktionieren.

Es klingt zwar unsinnig, aber DCS wertet auch die Lautstärkenregler am Radio und am Intercom Panel aus. Sind diese runtergeregelt, werden die Funksprüche nicht durchgereicht. Der Drehschalter am Intercom Panel entscheidet, welches Radio auf PTT (ThrustMaster Mic Forward) reagiert.

To explain the problem of Sticher: The attitude of an aircraft can be described with the three values of yaw, pitch and roll, expressed in degrees. Whereby yaw should not be mixed up with heading and roll cannot be taken as bank. Why? Imagine, an aircraft goes with heading 360, straight and level. In this case yaw, pitch and roll are all at zero degree. If you lift the nose by 100 ° then you cross the 90 ° vertical attitude and finally your nose points a bit backwards. If you analyze this attitude you will find that yaw = 0, pitch = 100 and roll = 0. But your heading would be 180. The magic behind is, how axis turns are handled. The standard for calculations is, first yaw, then pitch and last roll. If the sequence is mixed up, a complete different attitude would be the result. Another fact is, that the axis turns are not done around the X,Y,Z axes. They are done around the U,V,W axes. Where U is the lateral axis, going through the wings (pitch), V axis is vertical (yaw) and W is the longitudinal axis, going along the fuselage (roll). Now the surprise, if you maintain your heading of 360° and lift the nose by 45°, a subsequent roll is done around the lifted W axis (not Y), which has some confusing results. If we take an aircraft, flying straight and level on heading 180°. The question shall be, what values for yaw pitch and roll must be used to bring an aircraft into this attitude. If the standard sequence of yaw, pitch and roll is maintained, one solution could be: yaw 180, pitch 0, roll 0. But there is at least a second possibility: yaw 0, pitch 180, roll 180. Now the special behavior of the DCS values. In regard to the first example (yaw = 0, pitch = 100, bank = 0), as soon as pitch crosses the 90° border, they count the pitch backwards by switching to the second possibility: yaw = 180, pitch = 80, roll = 180, which results exactly in the same attitude. But a motion platform in this case, would almost kill a sim pilot by because the roll of zero switches suddenly to 180°. The only exact math solution would be to evaluate the content of the required 3 by 3 turn matrix, which contains the unique positions of the U,V,W axes expressed in Sine and Cosine. Regardless what yaw, pitch or roll was used. But this is a real tricky process which requires a deep understanding how matrices proceed. I am sorry, that I cannot help for the moment because my job holds me busy for the next time. But there could probably be a math genius in the community, who can solve the problem. To the other problem of side forces: In an exact coordinated turn, no side forces are noticed. Only the G forces are present which are felt as an exact vertical increase of weight. To simulate this forces, a calculation including gravity and centripetal forces are required. An exact simulation of the increase/decrease of G forces is not possible with a fix mounted simulator. Please apologize the length of this article. I had already direct contact with Stitcher in the past. I only want to specify the details for a possible solution.

I cannot make any estimate for the moment. Since I will start in my new full time job as ATC coach next week, I am busy with my facility rating which I have to finalize in a given time period. When this is done, I will make a new time schedule.

@John-John Just did the test under the described conditions and can now confirm a bug. If the Mirage is reentered after a crash, it experiences a frequency mess up. I did not find the reason up to now. It will be solved with the next release together with the F-5E support. Since I can reconstruct the situation, your log files are not needed. Sorry…

@John-John Hi John-John, I just tested this situation for the Black Sea version and for NTTR. The reported behavior could not be observed. The normal change to another aircraft and the change after an aircraft crash worked normal. Therefore, I assume a misunderstanding in the configuration or the handling. The only way to find the reason is to inspect the log files. Please do the following to create the required session logs: All participants, make sure, that the protocol application is not active (inspect the taskbar for an application with the Aries logo). If it is active, please close it. All participants, start TeamSpeak as normal. The protocol application is started automatically in the background. Start a DCS server or login onto a DCS server of your choice. You should be in contact with all participants in the common TeamSpeak channel. All participants, enter the aircraft of your choice. Unpause the mission Set the briefed frequency in your radio box and do a radio check. Now crash one of the manned aircraft. From the DCS screen, select a new aircraft and start it Set the briefed frequency in your radio box and do a radio check. If the bug (no contact) appears, make a note for the following checks: Does the blue carrier light in TeamSpeak come up when you depress PTT? Do the other participants notice the blue light in their TeamSpeak when you depress PTT ? Do you see the green carrier light on the Aries Panel when you depress PTT? Do the other participants notice the green carrier light on their Aries Panels when you depress PTT ? Send the following log files to my support address support@ariescon.com: C:\Program Files\AriesWings\PRCL\ApplicationData\Aries_Session_Protocol.html C:\Users\[user]\Saved Games\[DCS installation]\Logs\dcs.log I will inspect the log files an try to find the reason for this behavior.

@LuhanDula Your observations are basically right and my fellow pilots told me more than one time. Because we do not distinguish between the different types of transmitter systems and do not consider the individual transmitter power. It is prepared internally but not programmed finally. It is planned to have individual parameter for each aircraft in one of the coming versions. The current behavior is based on my experience what I have heard in my control tower. I observed roughly 3 states. One is a clear undisturbed reception. Only the clear identified voice modulation is amplified. White noise is clamped off. The second is a distance where the white noise reaches a certain threshold. At this distance, the receiver cannot differentiate anymore between the modulation and white noise. The entire reception, white noise and voice modulation, is amplified. With older receiver types, the white noise came into the foreground gradually. The newer, digitally constructed systems observe defined thresholds. This causes the white noise sound to jump in suddenly. The third is the distance at which the receiver decides, that white noise covers the entire voice modulation. That is the moment, the receiver switches off. Unless squelch is switched on. Furthermore, the terrain profile and the horizon are considered. As I stated, there is no difference between the systems. Therefore, the 5W and 25 W switch is not evaluated up to now. I hope, you can live with these limitations for a while...

see: http://forums.eagle.ru/showthread.php?t=126899 , post 10

@Hammer_nine_seven It looks like, that TeamSpeak cannot find the Aries DLL or the path to the Saved Games folder cannot be determined. Windows 10 has a restrictive security layer, which prevents the modification of the registry and the access to some folders on drive C. These limitations should be solved with the latest version of Aries Radio (V1.987M). If you use an older version, please download the latest version from http://www.ariescon.com/index10.html. I assume you made an uninstall of the old version instead of removing it !? To install the latest version, please go through the following steps: Step 1: From the control panel, open ‘Programs and Features’. Step 2: uninstall all versions of ‘ABradio’. Step 3: If exists, delete the entire folder C:\Users\[user]\Saved Games\AriesWings exists. Step 4: Delete the entire folder C:\Program Files\TeamSpeak 3 Client\plugins\AriesRadio. Step 5: Install the latest version of Aries Radio. If the installation does still not work: The folder, where the installation package was unzipped and started, contains a log file, created by the installer. Please send the file ‘AirbornRadioInstaller_log.html' to support@ariescon.com. I will evaluate the log file and will send further advice.

@charlesnett, We have finished the first performance and quality checks successfully. Since we need not to support concert quality, we can save a lot of network traffic. The next step is the construction of a simple sign-in method. These were the good news. The bad news are, that I will take over a fulltime job again. Therefore my 8 hours per day development will change to weekend development. So the entire project will take more time than planned.

@Esac_mirmidon, The tests for all three DCS versions were successful. The only possibility could be, that the installation was corrupted. Please check the existence of the following file in the DCS installation you used: C:\Users\[user]\Saved Games\DCS\Scripts\Aries_GameGUI.luac or C:\Users\[user]\Saved Games\DCS.openalpha\Scripts\Aries_GameGUI.luac or C:\Users\[user]\Saved Games\DCS.openbeta\Scripts\Aries_GameGUI.luac These files are necessary to connect to the required DLL for dual cockpits. If they do not exist, please create them and insert the following line: dofile(lfs.writedir()..'../AriesWings/GameGUIconnect.luac') Please let me know whether it solved the bug.

Hi Esac_mirmidon, I will test it out with my fellow pilots this night. Nevertheless, the handling of the radio in multiplayer mode is bound to the SPU-9 panel. Have a look, whether the radio control switch is in the forward position. Because of timing problems during the startup phase, it may be, that the switch comes up in the backward position. This means, that the radio control is lost. I keep you informed, TOWSIM

The only reason why I mentioned ‘full screen mode’ is the behavior of the windows Z-order. In full screen mode, it is impossible to keep the Aries Radio Panel on top of the DCS window. Therefore, Aries Radio should be used with DCS in windowed mode, unless the Aries Radio Panel in not required. Oculus rift is a complete other topic. The use with windowed mode or full screen mode should be answered in one of the oculus rift threads. @coug4r TS itself needs not to be uninstalled. Only Aries Radio should be uninstalled. It deletes all Aries Radio files to be sure, that there is no old leftover. This will not be necessary in future versions. Meanwhile I found out how to force the installer to replace the required files safely.

It is actually up to the users what configuration is used. The thing is the change of the default configuration between the versions, which can cause confusions. The radio application is not impacted by the configuration.

The normal procedure to start a multiplayer game would be, that all participants enter the game server, select an aircraft, enter the cockpit and then the game would be started by pushing the un-pause button on the game server. This procedure is valid with the configuration ‘Resume manual’. The configuration ‘Resume with clients’ un-pauses the game automatically as soon as a player enters the cockpit of an aircraft. We found this not so comfortable if one player is already in the running game while other players are still in briefing. The latter configuration caused a confusion on our first trial because ‘Resume manual’ was the default in older versions. After the start, the game behaves normal in both configurations. No restart is required, if someone leaves the game.

The “arm” button first deletes a previous setting, so to see an empty edit field. Now you need to push the button on the device of your choice. The edit field will then be filled with the device name and the button number. If nothing happens on the device button push, then you ran into a X55 issue with the Rhino software. The Rhino software prevents the normal signal passing. It sends whatever was defined in the Rhino setup. You should try to correct the Rhino setup or to deactivate the entire Rhino software. This should solve the problem.

Dear Aries users, A new version of Aries Radio is available for download. Users who run already version 1.987 may use the upgrade package. New users or users running an older version need the entire installation package. Beside some small internal bug fixes, we have included the M2000C model. All details of the M2000C Radios are described in the user manual. The new version supports all versions of DCS. The downloads are available at: http://www.ariescon.com/index10.html The upgrade package can be found at the bottom of the page (for V1.987 users only). The complete installation package can be found at the top of the page. Have fun…

I just tested it out and found no malfunction for FC3 aircraft. If no carrier light (green LED) comes up, then it points to a PTT issue. On seldom problem is the difference between common PTT and combined select/PTT. If you use the MI8, then the radio box 1 is selected immediately after mission start and you can use common PTT without an explicit box selection. With FC3 aircraft you need to select a radio box before you can use common PTT. If no box is selected (no yellow LED) then PTT is ignored. If this is not the reason, then it would be for interest whether other users have similar problems with FC3 aircraft.

Wenn für den Navigationstest ein FC3 Modell, z.B. F15C, genommen wird dann ist die F10 Karte, oder die Karte im Missions-Editor hinreichend. FC3 LFz zeigen Headings nach Grid-North an. Der Unterschied zu True-North beträgt etwa 1 Grad im Bereich um Nellis. Bei voll unterstützten Modellen wie die A-10C wird Mag-North angezeigt. In diesem Fall ist die F10 Karte unbrauchbar, da der Ruler nach Grid-North ausgerichtet ist. Der Unterschied beträgt etwa 12 Grad. Mag-North, oder irgendeine Referenz dazu, wird auf den F10 Karten leider nicht angezeigt. Mein Vorschlag wäre den Track und das daraus resultierende Winddreieck zunächst mit den Werten des Rulers zu bestimmen. Falls das LFz nach Mag-North kalibriert ist, muss von den errechneten Steuerkursen jeweils 12 Grad abgezogen werden. Beispiel: der Ruler zeigt entlang der Startbahn 03R, Nellis, 40 Grad an. Davon werden 12 Grad abgezogen. Das Ergebnis ist 28 Grad, die auf dem Kompass der A-10C angezeigt werden, wenn das LFz auf der Startbahn 03R ausgerichtet ist. Ansonsten kann ich sagen, dass das Nevada DCS Kartenwerk sehr genau der Wirklichkeit entspricht. Man kann die original Karten zur Navigation heranziehen.

Antiskid eingeschaltet ?

If someone uses the DCS map for navigation, he should know, that DCS aligns the map to grid North. All FC3 models show their compass heading with reference to grid north, not to true or magnetic North. The A10 and most of the other full constructed models show magnetic North on their compass. I explained the differences in a post found at http://forums.eagle.ru/showthread.php?t=126899 #10. In the attached picture it can be seen, that the exact vertical ruler line shows 360° (0°). This behavior is the same at all locations on the map, from far West to far East. True North is always along the meridians and changes from westerly locations to easterly locations. Magnetic North is bound to any given location and not shown on the DCS Map. It does not reflect the real world variation. The only way to find the magnetic heading for a given runway is to place an A10 as ‘takeoff from runway’ and read the heading from the HSI. On the other hand, all necessary information can be found in the DCS installation folder: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Doc\Charts. The charts contain precisely all necessary data for all aerodromes and visual approaches.

I will test this out. Under normal circumstances, Aries does not interfere with DCS voice com. It only checks frequencies and does not suppress any DCS voice. The only conceivable error source in connection with Aries could be too weak volume setting and/or incorrect frequency setting.