Saruman

+1. Brakes on, wheel chocks and ground crew screaming "What are you doing". As a result, you think you have payload, you see that payload, but missiles and bombs, when needed, do not leave pylon. I guess this bug would need some care, you waste a lot of time when ramping, taking off, cruising, only to find weapons do not leave pylons because of ground crew getting mad and not properly attaching it to pylons.

About new scripting function world.removejunk(). Which units are considered "junk"? The destroyed ones leaving wrecks?

I see now, thanks. Point stands though: did ED ask its SMEs too before adjustinf slew rate or did they rely only on video (of an unknown Lot in unknown conditions)? And, to sum it up after discussion, above all, are they going to at least accelerate cursor for all pages (SA, HUD, FLIR, etc.), so that everyone can easily customise curves on its own hardware once for all? Because I adjusted my curves to my hardware, radar is now again usable for me, but curves did adjust even for SA, FLIR, etc., making cursor slower than it should be, since faster slew rate was only applied to radar. Inviato dal mio BLA-L29 utilizzando Tapatalk

4) is the Maltese cross. If you see it all the time, you'd better turn on your radar, because it's off or SIL (or EMCON, but it's not implemented in DCS so far afaik). Or you are weight on wheels all the time and you never take off, which I hope not, you should enjoy this module in air, it's fun after all. (Coming back into topic, the plane in video could have been on ground and could be operated by ground crew for testing purposes, because bars were moving before Maltese cross appears on screen, so weight on wheels is a probable option). Point is: ED is known to be overly cautious to reference to real documentation, then makes a change basing assumptions on two secs of a video, totally out of context because we do not know anything about Lot it was filmed on or contingent situation? Posting that video again by BN, in this thread, as a justification for changing slew rate in sim (change only partially made, because they did not change cursor speed in other pages) does not get me very comfortable, to be honest. I would have been really ok with a more articulated answer by staff, like "This is a video we were being aware of, we asked our SMEs/consultants about the slew rate, SMEs/consultants confirmed the video".

Nope, at a certain point you can see radar is off or stby as a consequence of slewing (cross-symbol in lower left angle of screen) Inviato dal mio BLA-L29 utilizzando Tapatalk

Thing is that the acceleration vails only for RADAR, so, if you change curves, cursor in HUD, FLIR etc. goes slow like a turtle! Inviato dal mio BLA-L29 utilizzando Tapatalk

I guess it's emerging from discussion that we would all be happy if ED would accelerate all cursors in all pages or let all of us customise our general cursor speed. As it is now, it makes unhappy one user or the other for different reasons (no acceleration in other pages vs too fast acceleration overall).

Yes, mate, I'm debugging a bit. It seems it all comes down to a certain scripting framework. I'm looking into it to understand why (since campaign relies on that framework). I confirm that, with clean installation, server works fine, but there are some incompatibilities with my actual script environment.

Not for me. Server does not come anymore up in server list, I cannot reach it by connecting to IP (DCS tells me it is offline....) and, besides, scripted missions with Moose and dynamic loading of the framework do always crash. Reverting to so-called "deprecated" version. P.S.: it's a 24-hour campaign server, it worked flawlessly before I had the unhappy idea to upgrade it to newest version.

Yes, they intended to do that, it's in the patch notes. Reason is a 2-years-ago request on F18 forum by some users, supported by 2 seconds of a Youtube video where cursor, on an unidentified BUNO and model of F18, slewed so fast, but you could not understand, by watching those 2 seconds, if radar was in test mode by ground crew (radar was turned off by simply slewing in the video, that's very suspicious) or if it was in actual working mode (I hope ED asked their SMEs for confirmation before the change). Some users are now even asking to fasten FLIR and SA cursor too on F18 forum (request was moved in wishlist by Nineline). I cannot fly anymore proficiently F18 due to this change and I am really furious this time with ED, because I support the team by buying a lot of modules and I would have appreciated a more reasonable and mature approach on this 'feature'. Even if real slewing should be so fast (and it's an 'if', until an official statement about confirmation by SMEs), we are on a sim, not on real plane with real HOTAS, therefore we emulate the real thing with a limited hardware and not a lot of us own a top-tier 350$ throttle with sensitive hat-switch for slewing, so a custom slider for slewing speed would have been a more intelligent and inclusive customer-care solution by ED. Saturation and curves on axis are not a real solution too, because you can indeed limit a bit the actual speed of cursor on radar by playing with them (I did it setting saturation to 60/100), but cursor moves like a turtle on SA and FLIR page then. Besides, ED seems to have forgotten that they implemented TDC slewing by keyboard bindings too, so they let user theoretically slew by keyboard. Well, I challenge ED's staff to slew by keyboard the cursor with the actual lightning speed. Inviato dal mio BLA-L29 utilizzando Tapatalk

Same with Mk82. No CCRP line in Auto, it always launches in MAN Inviato dal mio BLA-L29 utilizzando Tapatalk

It's an intended thing. Problem is they didn't consider people use different hardware and keyboard too, so they should have implemented a customisable slew speed instead of this... I'm really curious if ED asked their consultants before the change or made it only because of 2 seconds of a video on Youtube with radar slewing so fast without even knowing which model of F18 was depicted or if the radar was in test mode by ground crew (the slew turned off the radar in that video) or the aircraft was actually airborne. Inviato dal mio BLA-L29 utilizzando Tapatalk

Yeah, I played with saturation and reduced it to 60/100 and it's fine again. But now FLIR and SA go too slow, so it seems you are up to do a choice if you don't own a top-tier throttle with proper TDC hat-switch. I can see why ED considered the slew speed should be changed; I can't see why they did not think different users have different hardware though and need to adjust and customise the sim to it. In theory, DCS lets user even use keyboard for slewing and this huge actual acceleration makes the keyboard assignments useless as well.

Best option would be an option to let the user decide slew speed. On X52's minimouse the actual speed is unbearable.

As per object, since latest update AI F14 taking off from Forrestal do not generate any takeoff event or, at least, event.initiator is a nil value. This breaks a lot of script stuff and triggers checking for F14 taking off. Other planes work well.

Could we have at least an official statement about ongoing investigation even after patches? Thanks guys, I know you're busy, but a word from you @ED would be nice.

Attaching a picture you can notice the problem from. MFD on the left is exported the right way, main view seems fine, but look at placement of ATC subtitles..... and all overlay texts that should appear on the right do not appear at all. Because of that, I cannot even do any tutorial... EDIT: After debugging, I understand what's happening. I have two monitors: the little one I export to, on the left (even in Windows), and the main wide one. Coordinates of main viewport begins at x = 1025 (the little monitor is 1024x768). Now, DCS-MT correctly renders on the main monitor with those coordinates, but, for the overlay and subtitles, it does consider x = 0 on the main monitor (!) and so it applies +1025. Consequently, overlay and subtitles go off screen. If I move the little monitor from the left to the right, so that the main viewport is rendered on the main monitor on x = 0, overlay and subtitles work correctly.

+1, even after deleting fxo/metashaders and repairing. Same issue Inviato dal mio BLA-L29 utilizzando Tapatalk

It seems the GUI problem was not solved by hodiern update. Dialogues are still offscreen.

+1 This same thing happened to a friend of mine (to me it happens in MFD, instead, there's huge mosaic on the right)

I know about the ghosting problem with MT. In my case, there's also an artifact problem though (see attached image, on the right, all those coloured lines). null

I think it would be nice if, for every module, we had some short clips running in background in main menu, starring the theme module, instead of the still images we have at the moment.

At the moment, when you spawn in cockpit, you find that the aircraft imported automatically up to 50 non-hidden anti-air threats in the COORD page, taking them from the ones present in Mission Editor. Now, it could seem a feature, but it's clearly a bug, because on very large mission (like the ones running on more famous public servers) you have a lot of mess with those auto-imported threat points, while all you would like is an aircraft in a clean state. Auto-import of threats from Mission Editor should be therefore disabled or, at least, changed to an opt-in/opt-out system, letting mission designers and/or players to choose whether they want to use it.

Can't check right now but irrelevant. It's a gpu-less headless dedicated VPS server running smooth until updated to 2.8. It's not a desktop. 2.8 is clearly the problem. EDIT: I tried to remove Awacs from my complex running mission on the server, just out of curiosity. CPU usage went consistently down. I guess Awacs is doing something weird in new release under the hood? Inviato dal mio BLA-L29 utilizzando Tapatalk

As per thread object, 2.8 performance on a gpu-less dedicated server VPS is horrible, CPU is always throttling between 80%-100% regardless of number of clients connected, with intuitive consequences on lag/freezes (like Awacs or tankers being still in the air). On 2.7 CPU was very low on usage and server was pretty smooth. No mods of course. Inviato dal mio BLA-L29 utilizzando Tapatalk