Rongor

Apparently this didn't change anything here. Also I have it checked by default.

Den Preis haben sie noch nicht genannt, nur die erst einmal grundsätzlich die Möglichkeit in Aussicht gestellt. Wird jetzt aber erstmal noch nicht dazu kommen. Denn ich hab die Throttle-Einheit von unten geöffnet. Scheuerstellen oder andere Beschädigungen im Bereich des Kabelbusses der vom rechten Schubhebelaustritt waren nicht feststellbar. Das Ding war dabei unter Strom, so konnte ich bemerken dass das Fehlerbild verschwunden war. Ich nehme mal an, dass die Kabel irgendwie eingeklemmt waren und irgendwelche noch nicht sichtbaren Brüche die Signale kamen. Obwohl jetzt erstmal wieder alles funktioniert wie es soll, rechne ich daher mit baldigem Wiederauftritt des Problems. Bis dahin warte ich mal ab.

Lino, mit Verlaub, 30 MHz bis 76 MHz ist ein riesiger Frequenbereich. Alles zwischen Kurzwelle und UKW-Rundfunk ist darin enthalten. Der Bereich wird in der Realität sogar hauptamtlich für Sprechfunk eingesetzt. Das Homing das wir mit dem Huey in diesem Bereich betreiben ist eher ein Abfallprodukt und der recht simplen Konstruktion entsprechender Peil-Missionen geschuldet. Das Sprechfunkgerät soll die Bodentruppe eben auch anpeilen können, damit man die Jungs im Dreck mit dem Helo besser findet oder suchen kann wenn sie sich verlaufen haben (oder abgestürzt sind). Wenn der Sprechfunk bisher bei Dir nicht funktioniert, denke ich auch eher an ein Problem in der Konstruktion Deiner Mission. Lad uns die mal hoch. Das Gerät wartet nur auf Sprechfunk, dafür ist es ja da und verfügt extra deswegen über genau diesen Frequenzbereich;)

The situation you described shouldn't be possible. Did you hear an ident tone? or did you hear a steady tone? Steady tones are steady and not intermitted like morse ident tones. What kind of mission did you start? Does it include transmissions which could sound like that? If you switched off all your 5 radio receivers and one tone continued, it is a warning tone generated by your aircraft. By the way, there is absolutely no sense in not turning that TACAN ID off. Why would you want to listen to these beeps while flying and attempting to AAR? No real pilot would listen to any of these ID tones longer then for a few seconds, for their one and only purpose, to ID the received radio transmission. You can switch TACAN and ILS audio off with a single right click on the respective dial knob on the intercom panel (therefore pressing them down) after you successfully ID'ed your signals. Don't waste time in turning all those volume dials down. Same functions with the three voice radios. Only way to have radios generate a steady tone is to set frequencies out of their bounds or to receive something wich delivers a steady tone because the mission editor implemented it that way. As far as I believe to know, homing is not modeled in the A-10C, but I am willing to be taught otherwise. Let's see what others have to say...

Mir bieten sie gerade einen Austausch der Platine im rechten Schubhebel an. Fürchte nur, dass das an meinem Problem nix ändern wird. TM hat also tatsächlich geantwortet, sogar auf deutsch. Englisch wär ja auch kein Problem gewesen aber wenn sie schon deutsch anbieten... Haben mir ein PDF gemailt indem beschrieben ist wie ich den rechten Schubregler auseinanderbauen kann um die Steckkontakte an der Platine zu überprüfen. Da ich auch eher Sobek's Verdacht habe, werde ich das Ding zunächst mal von unten betrachten. Leider keine Anleitung für gefunden.

I am facing the same problem recently. The first unlocking of throttles doesn't work. I have to move them back into the off detent and then forward again to start the engine.

Probably only to serve the thread title :D Other than that, it may be necessary if you reached your maximum of storable markpoints or for constructing flight plans in the CDU. But as I never use this feature, I also omit that part mostly. You are absolutely right, markpoint does it also. At least for us ;)

link mal so'n video, sonst ist das schwer zu beurteilen...

Habe am rechten der beiden Schubhebel (Z-Achse) bei mehr als etwa 80 % Schub auf allen der am rechten Hebel angebrachten Buttons Phantomsignale. Drücke einen Button willentlich, kommen flackernde Signale zustande, die dann auf andere der Buttons 3 bis 12 übergreifen. Somit ist eine Steuerung zB der MFCDs und SOI-Wechsel bei mehr als 80 % Schub nicht möglich. Hab den TM-Support gestern angeschrieben, noch keine Antwort... Hätte von nem Produkt in der Preisklasse mehr erwartet, bin vermutlich der Einzelfall.

:) Glad to hear you guys like this approach!

:thumbup: Good news, now enjoy some flying!

Great!

Won't happen within the next 5+ years, probably never. Welcome to the forum!

Darf man fragen warum? Wenn man bedenkt, dass Du hier ein Produkt anbietest, dessen Garantiezeit abgelaufen ist, erscheinen mir nur 25 % Preisnachlass gegenüber einem Neukauf relativ unrealistisch. Meiner zeigt nach drei Jahren erste Mängel.

if the whole folder content is missing, we would have to ask where all your DCS missions and profiles and other essential stuff are stored instead. They have to be somewhere, otherwise you would have a hard time starting DCS up. Find that location and then you will be able to pursue your plan. Did you navigate to the right windows user profile? Is there anything weird about administrator rights on your PC? Solve these questions and everything will be fine. You could also simply search your hard drive for the export.lua file. Took me less then one second to receive the location.

While I agree that ED just too often created the appeal we would face EDGE "soon", I absolutely don't see why you don't enjoy wonderful aircraft modules in the meantime, only because of a lousy logbook function...

http://forums.eagle.ru/showthread.php?t=140870

ATC has lots of issues in its current state. Since it is also nowhere near real world content, better ignore ATC for now. I do use it sometimes, but only because it is routine to do so. If it doesn't work, simply disregard ATC completely.

Wouldn't the computed angle result from the waypoint you are coming from, respectively your current 3D position?

shouldn't matter. mouse pointer should change even in paused state.

Before maintaining to wild guess and reinstalling drivers or DCS World, simply look up the right key combo under options>controls>A-10C Sim>"Clickable mouse cockpit mode On/Off" Default setting for "Clickable mouse cockpit mode On/Off" is LAlt+C If your mouse cursor stays yellow and nothing is clickable inside the A-10, you probably climbed into an A-10A cockpit by accident.

I use a different approach without fiddling around with the CDU by using the TAD. Precondition: You have to have something hooked in the TAD to enable cursor data display in the lower display area. I assume the TAD being SOI. After receiving bullseye data, use OSB 18 to switch to BULLS/CURSOR to receive a bullseye coordinates readout for the cursor position (if not set already). Then steer the cursor to the called out coordinates. After that I press TMS right short which creates a markpoint at that position. Now I simply do another TMS up short, which now hooks that new markpoint (as the cursor will still rest on that location). Now you can press OSB17 and create a waypoint on that markpoint location. Done! If you turn the dial on the CDU to markpoint, you can also omit that OSB17 step entirely and simply use the markpoint as steerpoint. That would reduce workload after setting TAD as SOI to navigating the cursor to the bullseye coordinates and a single TMS up right. I absolutely agree these workflows are very much personal taste, but I find my way to be quicker for me. Also it keeps me able to do it both ways. I can easily tell bullseye coordinates of other found targets I "stored" on my TAD, which wouldn't be possible by that CDU usage at the same amount of steps.

Since about two years their announcements sound like EDGE and stuff is waiting right behind the corner so newsletters like this one - so appealing they might be - don't impress me anymore. Finally release something, THEN I can be happy (maybe)...

So you did 2 different downloads. One download had corrupted files, the other didn't. So this is in any way evidence for a technically weird statement? The "harm" done is the confusion you spread by claiming any connection between your successful second download and your use of two different downloaders. Your simple judgement to bear the second downloader "better" than the first one is in no way justified by this. Downloaders aren't responsible for corrupted data streaming aboard your computer.

These are two different statements. Corruption of files is not the fault of your download tool. Its job is to download stuff, not to verify its integrity. Files may be corrupted, but your downloader didn't lie when tellling you it completed the download.