All Activity

But do you see when the aircraft is with LAU-129 and full AA ordnance (LAU-129 in stations 4,6 empty) is CAT III, and with LAU-118 is CAT I? For me seems strange.

Update: Revised the "eyeball" to 'x_trans = 0.122000', as it still 'pops', but seems to run faster/smoother. The little things. SnapViews["P-51D"] = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 54.750000,--FOV Cockpit Zoom 54.750000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (Snap View)/(Cockpit panel view in)(-30°) vAngle = -30.00000,-- Cockpit View Angle -30.00000, OEM -9.500000 x_trans = 0.122000,-- Cockpit View In_Trans 0.122000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, [13] = {--default view viewAngle = 40.000000,--FOV Cockpit Zoom 40.000000, OEM 80.000000 "P-51D" viewAngleVertical= 0.000000,--VFOV hAngle = 0.000000,-- (View Center)/(Cam View Dn-Slow)(-30°) vAngle = 0.000000,-- Cockpit View Angle 0.00000, OEM -9.500000 x_trans = 0.122000,-- Cockpit View In_Trans 0.122000, OEM 0.120000 y_trans = 0.060000,-- Cockpit View Up_Trans 0.060000, OEM 0.059000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, Enjoy. Bowie

Yeah this is a huge disappointment for the Black Shark. Especially in vr and a hover attack helicopter as unlike a fast mover you can be eyes in cockpit for long periods of time

Same problem, cant fix it... Anny other idea? THX

I noticed a strange issue with the rdr cursor when revisiting the sniper pod and mavericks. For slewing the cursor round in the MFD's (all modules) I use a little thumbstick on the side of the Saitex X52 Hotas throttle unit. I set the Y-sat and sensitivity way down to get a nice smooth slew rate. In the F-16 TGP and Mavericks I noticed the cursor keeps drifting vertically upwards, even when I try to fix it to a ground object. If I map this to keyboard presses (eg: U,D,L,R cursor keys) it remains steady and fixed, until I use the thumbstick for the x & y axes again. The thumbstick does not have this bug in any of the other modules (F-18, Apache, Harrier, F-15e, KA-50). I checked for any axis conflicts but there are none. Any ideas I can try?

They already stated that they are working on the F-104 in parallel of the F1M and Radar Overall. They are a small team and they are increasing the quality of their current and future product. Let's be patient and wait for a good module. I'm pretty sure they are eager to share news aswell. "Let Them Cook"

Please god let those unit/language options be added to the special options tab.

Excellent! You have some sort of corruption in one of the folders. The consensus seems to be some sqlite file in the Mission Editor folder. Pinging @sleighzy for the details. Delete that file, and you can revert back to your backup folder, so you don't lose all your bindings and your logbook. OR just copy back the input folder, and the logbook.Lua from the Mission Editor folder on the backup. Cheers! Sent from my SM-A536B using Tapatalk

Ja genau, der wird über den Joystick und das Ruder gesteuert.

+1 for a better monical for 2d users.

I thought I had convinced you on mod managers? [emoji6] Sent from my SM-A536B using Tapatalk

There are system failures, but not preset/specific system failures by custom triggers. Turn on "Random System Failures" via Options->Misc. menu. Something somewhere might break but not cockpit lights which afaik only the F-4 does it. It might ruin a whole sortie depending on the system that failed.... or greatly enhance it depending on the mindset, ofc.

@Ornithopter Fair enough! I actually re-read the whole thread and it got me thinking. I know I bring up the radar a lot, and they even address it in one of the posts. I have a feeling they will use the "same" radar model in the F-104, which makes perfectly sense. And they might have started on the F-104 in parallel, which could be a reason for the "delays". Cheers!

So, gerade mal probiert und nachdem ich beim ersten mal ejecten prompt in einen See gelandet bin konnte ich beim zweiten mal den Pilot mit den Pfeiltasten laufen lassen.

That would actually be a very good idea just to be sure. Other players have had the weirdest issues; in some cases they swore they never installed any mods, yet renaming Saved Games\DCS and allowing DCS to recreate it solved their problems. 100% what MAXsenna said, you can copy individual folders like Saved Games\DCS\Config\Input or Saved Games\DCS\MissionEditor\logbook.lua back once DCS recreated the Saved Games\DCS folder for you, and likewise for liveries etc. Like MAXsenna already said, every change to the folder structure and files in Saved Games\DCS requires a restart for DCS to register the changes. I'm not mad. But when the advice is "remove all mods" and you say "Yeah I'd rather not do that", I simply don't know how else to help you. There's still every chance the issue has nothing to do with DCS and it's something with your graphics card or the graphics card driver or an odd combination of things to do with Windows and drivers and settings and DCS that is going to be extremely hard to resolve. But it's also possible there's a combination of mods or mod-leftovers in your Saved Games\DCS that would make any DCS installation crash, and that's something that you can test with relative ease - especially when you take the opportunity to move to a mod manager that will most likely save you a lot of time in the future, regardless of the outcome of this issue.

Try here to see if it answers your question This is what I know but I have not flown in since.

Yeah, I know. I just wanted to emphasise that it is a bug. I haven't tried it yet, but I assume it's OvGME compatible, and then OvGME will unzip it correctly to the relevant folders. @fagulha can you confirm? Cheers!

CH. Thank you for your hard work creating these assets.

+1

Warum nicht? Beide Antworten waren Volltreffer.

As people that flew IRL said, the vanilla HUDs in DCS are spot on. I only now HUDs from photos and tried to match those in my mods

Update v1.1.4 Hello guys, before I get completely lost in studying for the exams, I would like to drop a stable update with no known bugs and with some minor adjustments. It's a smaller patch, with adjustment to the max fuel weight (it was corrected to 16350Kg), countermeasures number and little SFM adjustments, and I'm releasing it just so that everyone is on the same page, before the update drought. Regarding further mod development - it will start again when I will have more free time (basically whenever the semester and exams end). Enjoy!

No opinion, just saying that it *could* be a contributing factor. I don't know if it affects it for a fact.

Well, of course you would have, because that is the courteous thing to do, and you're probably a polite guy. The +1 stuff earlier, and the back and forth that followed would have alerted you to the fact that some people are getting annoyed. And then you would come on to the forum and say, Hi guys, sorry for the lack of news, but we've been busy working on X,Y,and Z. That seems like common sense, because a few sentences would probably cause this topic to go dormant again, or at least cancel some of the negativity. And yet, they've let it drag on with nary a word, to the point that the ED moderators are now taking notice and telling people to dial it back. Why aren't they addressing the commotion themselves? I too approached this thread with the attitude that people were being a little too demanding, and that they just need to shut up and quit pestering the developers, but as I've seen the thread play out, with no logical response, I've changed my mind. To me, something seems a little off. Hope I'm wrong.

Ah, sorry. Ich hatte das in deinem vorherigen Post überlesen und das so interpretiert, dass Du immer noch an einer Lösung interessiert bist. Naja, auf jeden Fall weißt Du was Du machen musst, falls das Thema bei Dir noch mal aktuell wird. Ja, sollte man im Jahr 2025 meinen... Für DCS hab ich das ehrlich gesagt nie ausprobiert. Allerdings kann ich weder über das GUI Servertool vom dedicated Server, noch wenn ich einen Server ingame hoste irgendwo eine IPv6 Adresse finden. Der Server übermittelt nur eine IPv4 Adresse. Es gibt also (zumindest über die GUI) gar keine IPv6 Adresse, die man irgend jemandem mitteilen könnte. Da man mit Dual Stack aber sowieso beides, eine öffentliche IPv4 und eine öffentliche IPv6 Adresse bekommt, kann man dann auch gleich den Port über die IPv4 Adresse öffnen.