All Activity

My understanding is that if you perform a fix on a Bx point, it moves every single point in the nav system by a corresponding amount. If you perform a fix on an Mx point, it only moves the Mx point to the fix, and not the rest of the navigation points in the jet.

e.g. In our squad we have all installed this skin. The livery can be installed in your user-folder and will be available as an additional livery, therefore not breaking pure skins and servers decide for themselves what they allow and don't allow, so on Enigma's/Heatblur's and other servers we can use it. For the MiG-29 Fulcrum It is even possible to change the pilot (e.g. change helmet) as an extra cockpit option (besides English/Russian/...) without breaking pure skins, but that will not be visible from outside the cockpit-view, e.g. when making recordings. So there are more skinnable aspects to the game in various directories with different rules. That should be much easier.

Could someone explain why hovering a full GW 9500 lbs Huey at Batumi in 20°C OAT requires 43 PSI Indicated Torque in IGE at 5 ft when UH-1H manual states 37.3 CT is only required?UH-1H_Hovering_PA 0_OAT 20 C_GW 9500.trk

Good call @Tholozor, but then the LAU-118 pylons for stations 4 and 6 are more suitable for CAT I than LAU-129?, I would understand the other way around.

What’s the point of using custom liveries online? Nobody else will be able to see them as it’s unlikely they will have those installed. My guess is Pure Textures are enforced to prevent cheating.

Just tested on my DCS and the Mod seems to work with no issues, this is the test mission setup: The aircraft is set as player, and this is when the mission is run: Post your dcs.log file, to look for more clues.

Ich habe ein ASUS MB mit X670E und bin sehr zufrieden.

ty i have pasted it on to the man that dose our server

null Which version of scriptsMod are you using? Because I did indeed have a major bug with weather generation. However, it doesn't sound like what you're describing. Can you push your mission here? In the screenshot, I posted the settings needed for bad weather, but with 50/50 it could be mixed.

That's right, tested, works great. I have an idea for a mission thanks to this. Thx.

@Wags wait, why is this post in skin wishlist? this has nothing to do with a skin, but with the functionality of the F-16 AG radar modes depending on loadout. nothing to do with a Mig 29 skin...

Hi guy... I've the same problem: I put some statics on carrier near the ramp1, but it seems that the ramp is stil active...

Moin, ich habe nun seit Anfang des Jahres ein Projekt auf meiner Bank liegen und stecke quasi genauso lange in der Klemme ohne Fortschritt. Nach Vorlage von Matbog vom französischen CheckSix Forum, habe ich mir die passenden 3D-Druck Teile für einen M-2000 Stick bestellt und muss dafür einige Gewinde in den größen M2,5 und M3 schneiden. Bisher mit einem Windeisen und Vor-, Mitten- und Nachschneider gearbeitet, bei den Resin Teilen kein Problem, aber die Metallteile machen mir zu schaffen. Aus zwei Sets HSSG Gewindeschneidern sind mir bisher drei Stück zerbrochen, wobei die Reste der Schneider in den Teile stecken blieben. Also meine Frage: Bevor ich mir jetzt noch ein weiteres Set bestelle (und es wahrscheinlich kaputt mache) wollte ich doch mal fragen, ob man so etwas auch irgendwo machen lassen kann oder ob es eventuell bestimmte Schneider gibt, die ich mir kaufen sollte? Falls wichtig: -Die Teile sind bestellt über JLCPCB und in SLM(Metal) gedruckt -Zum Schneiden habe ich SX90 verwendet

Remember that the pylons that the aircraft has loaded are different as well. With the air-to-air loadout, only the LAU-129 rails are present, but in the air-to-ground loadout, you have LAU-118 rails for the HARMs attacked to MAU-12 racks. The SMS is aware these pylons are present, which could be contributing to the CAT STORES condition.

Please @BIGNEWYhave a look at it please, two equal final states but with two different behavior from FLCS. If it is correct as it is, then what is the logic behind?

Whoa! So it's a really old issue (that somehow I've never noticed before ) that had been fixed at some point, but got broken again... Hmm... So, should I add a new comment on this older thread? Or do I keep this thread here open?

M47 variants, m48 variants, m60 variants, leapord variants, ypr 765. M102 howitzer, love how you do the m777 towed howitzer. Nike Hercules. Thinking of these we actually already have a good bit, and nato didnt really have the range the Warsaw pact had. More Warsaw pact would be nice too. Rm 70 and ot 64. Spg 9 would be cool. 2s7 and all the Soviet towed artillery. Infantry of any kind. Although I know that's very primal in DCS. M47 variants, m48 variants, m60 variants, leapord variants, ypr 765. M102 howitzer, love how you do the m777 towed howitzer. Nike Hercules. Thinking of these we actually already have a good bit, and nato didnt really have the range the Warsaw pact had. More Warsaw pact would be nice too. Rm 70 and ot 64. Spg 9 would be cool. 2s7 and all the Soviet towed artillery. Infantry of any kind. Although I know that's very primal in DCS.

Having custom skins for a squad is quite tedious and when fully implemented, every player even has to make changes to texture files that will break 'pure textures' so you can't play on multiplayer servers. It would be nice to be able to make one 'package' that people can install in their user folder and be done with it. It should not just change how you see yourself in the cockpit, but also how others (which have the same mod) see you, without changing core DCS files.

How are the tablets set as monitors? It would be helpful to know if they're using something like screendesk to emulate virtual monitors, have natural monitor thingies, or what have you

Saved games/DCS/config/input If your device ID's change you may need to change the file names to get them back into game. There are a few files around to automate that process in case you need to use the backup.

With the ASC C-130J coming ... a must have is the M-551 Sheridan! I dropped my share of those back in the 80's. I appreciated you putting it in your USA Assets Pack mod.

Habs kapiert. War anfangs nicht ganz einfach, weil ziemlich konfus was AMD hier mit labeling veranstaltet hat. Mein Fazit: Hauptsache ein E. Der Rest ist echt fürn A... oder fürn Geldbeutel, allen voran der neuen 8..er. Ich möchte also gerne ein E kaufen! Asus ROG Strix B650E-F für 160€ B-Ware (Sparfuchs option) Asus ROG Strix B650E-F für 180€ Neu Asus ROG Strix B650E-E für 220€ B-Ware (hat eigentl. alles) MSI MAG X670E Thomahawk 180€ B-Ware (wenig USB-A am I/O, keine DeBug Segmentanzeige:( ASRock B650E Taichi Lite 265€ B-Ware (overkill für X3Ds) Hab schon die absoluten P/L Kracher rausgesucht würd ich sagen:) Schwanke zwischen allen! Aber enger zwischen Asus B650E-E und dem X670E. Ein Asus ROG Z490E hab ich aktuell und bin zufrieden bis auf das Ai OC gedöns und dem aufdringlichem Softwaregehabe.

Precisely. And this is what the OP described pretty well, which is not a new problem, sadly.

page 160 (but not write about Bx): Navigation points (B1-B9) points and target waypoints (M1-M9)are handled slightly differently. In general one can state that a normal navigation fix is to update the status of the navigation system, whereas the target fix is to update the position of the target "in the real world" But if I use Radar fix, Bx handled slightly like B1-B9 and update the status of the navigation system. Maybe Bx must work like B1-B9 in Visual Own-position fixes too? Sorry if I wrong.