funkyfranky

Oh, dass klingt gut :)

Roger, wilco :thumbup: For now, I did the un-plug & re-plug trick and it solved it again - for now. But I reckon this gives me just another two-three months before I have to do it again. Still a great product. You have any idea what is causing this issue? Only logical explanation I have is that due to the movement, some connectors get slightly loose as others have mentioned already. But that is just a guess, of course.

And this is still a very impressive change log with some interesting new features. Thanks to the team!

:music_whistling:

Dann umso besser :D :thumbup:

AI On/Off hatte Viper doch schon erwähnt. Aber das Problem war, dass der Carrier dann nicht auf Funksprüche reagiert, wenn die KI aus ist.

This forum obviously needs a function to monitor when certain people post not just threads.

Q-Ball, just to make sure, did you set your aircraft to "Client" (not "Player") in the mission editor and did you hit "ESC" twice before entering the aircraft if it's a single player mission? If not, the script will not load due to a four year old DCS bug.

Any news on this after more than four years?

Yeah, looks like there is something strange with the pseudoATC. I'll have a look. Might take a few days though.

And here we go again :( Everything was fine since I re-plugged the connectors. Now two months later the issue starts to come back. Not yet as pronounced but I reckon that will will come. Anyone opened a support ticked about this issue or can tell me the best way to do it? Is anyone from VKB following these forums and make a comment on this problem? This is not really what I expected from such a high quality piece of hardware.

After a turn one of the escort ships crosses the path of the carrier. The carrier reduces its speed (to avoid a collision, I guess) and comes to a complete standstill. However, after the escort ship passed the carrier, the carrier does not resume its route. At this point the whole strike group gets stuck terminating the mission as the carrier will not proceed to the following waypoints. I have witnessed this now on multiple occasions. Attached a simple mission file. It happens at waypoint 3 a bit later in the mission. Track also attached. Also made a short video. It's a different mission but same phenomenon. Could we please release the drunken skipper from its duty? Thanks! DCS 2.5.4.30386 CarrierStop.miz CarrierStopBug.trk

Well done, lads!

Yeah, I wanted to post just that in the Carrier module thread. But well...

When I created the mod, the "lua based" method was the only one working. Nothing more, nothing less. I was not even aware, that you can now simply put them in the Saved Games folder ;) But that's even better :) BTW, credit for the background goes to HB. I shamelessly used what was already in the Viggen folder :D :music_whistling:

ED has to decide. This thread is people voicing their opinion that they prefer polished modules and core engine rather then new stuff. Basically some ask for a shift in priorities. ED want happy customers and make money eventually. They cannot make everybody happy of course, but when people are not happy with the current route, they should say that in a mature manner. I'm sure ED will listen and make their decisions in their/our best interest. But they probably also have to consider circumstances we might not be remotely aware of.

As with new modules, maps etc the workload surely is steadily increasing, what about the man power? Are you bringing new guys in or does the same number have just to handle more projects or are withdrawn from other project?

Per Skript oder nur ME Klicki-Bunti? Mit Moose Skript wäre es z.B. relativ einfach.

Great work. Looks stunning!

Jap, steht auch in der Videobeschriftung "NOTE - This video is a joke, but I have switched to only making REAL tech videos, see some here " ;)

Has this been fixed?

The findPathOnRoads function fails to find a path in a simple situation near Beslan, cf image.

Thanks for keeping an open mind :)

Nachtrag: Gerade noch mal im Uhrenladen Viggen (und Tomcat) unterwegs gewesen. Instrumente sind deutlich besser abzulesen als in der CV1. Macht richtig Spaß. In der Viggen musste ich mich ein bisschen nach vorne lehnen, um den aktuellen Wegpunkt B3 zu erkennen. Die 3 ist schon recht klein/etwas unscharf, wenn man normal sitzt. Aber selbst die Beschriftung des Weapon Selectors auf dem rechten Panel kann ich jetzt ganz gut lesen :) Im Vergleich zur Pimax funktioniert ja auch der VR Zoom ohne weiteres.

Hab die S gerade zum ersten Mal auf :) Die Pimax ist schon noch einen Tick "klarer", was die Bildqualität angeht. Nützt einem aber herzlich wenig, wenn die "smoothing" Software noch nicht ausgereift ist und man oft ghosting/judder hat. Ich glaub, wir haben genau die selben Erfahrungen mit der Pimax bis jetzt. Oculus ist, was das angeht einfach weit voraus - obwohl DCS noch nicht mal ASW 2.0 unterstützt. Die S trägt sich auch komfortabler als die Pimax (YMMV). Also von der S bin ich bis jetzt sehr(!) angetan. Deutliche Verbesserung im Vergleich zur CV 1. Einziges Manko was mir bis jetzt aufgefallen ist, ist der Sound. Das war aber schon vorher klar. Bin mal gespannt, was Du zu sagen hast, wenn Deine da ist.