ScopeDope

Question regarding AJS37 template. The google drive link above only has FUSELAGE_1 / FUSELAGE_2 / FUSELAGE_T. Where are the others? I realize this is in the F-14 thread but I don't see the Viggen paint template linked anywhere else.

Yes to this! Another idea I had was special options for each catapult. That way you could switch off 1 and 2, have aircraft park on the bow, etc. When all 4 cats are switched off, you're in pure recovery mode.

It's only been 2 years guys, give them some time!

+1 on my Index Also happened with an F-16 in a hangar at Al Dhafra

It appears that having 1 more AI set to late activate than the deck can allow, causes FPS to drop from ~50 to ~10 in my case. I have tested by removing/replacing the extra aircraft and the issue re-occurs. The FPS monitor shows severe activity in the core engine when this occurs. 2 track files attached, one for each scenario. CVN FPS drop.trk CVN FPS nodrop.trk

You do realize that the moon also has a rise/set time don't you?

+1

Love this idea!

±1 to the launch/recovery phase switching. Even if there is some kind of scheduled "mode" that can be applied in the mission editor.

+1 It's obvious that the carrier is assigning specific spots based on spawn sequence. Why not give that control to the mission editor.

I concur, this should be included in some kind of advanced action in the mission editor.

Same issue here. 1080 and Index. I want to say that I had the same issue inside a hangar at Al Dhafra in an F16, I can double check that it was the same issue and report back.

1 ) Polygon trigger zones 2 ) Undo/Redo 3 ) Unit engagement options such as burst fire with intervals (right now infantry basically shoot full auto for 2 minutes until out of ammo. Ideally a more paced, shoot a few times, take a break for 30 seconds, shoot again kind of deal would be nice so that a firefight actually lasts a while, and ability to set ammo quantity). 4 ) Blind fire for AAA guns ala Baghdad 5 ) More callsigns! (here is a link to a few thousand ideas - http://www.monitoringtimes.com/MilitaryCallsignList-APR09.pdf) 6 ) Mobile Tacan (I guess that might require an asset to be created) 7 ) Ability to export triggers to another mission 8 ) Lasso select edit after reading some others: 9 ) Multiplayer slots at airports! Revamp the slot selection page, it is far too tedious for a 2020 software. Select airport, select airframe, optional select specific slot (map with a little red dot or something here for bonus points), done! 10) Force AI taxiway movement. Example: taxi from parking to end-of-runway inspection spot, remain there for xx minutes, take off. Or start engines, remain in parking spot for xx minutes waiting for rest of package, then taxi). 11) Force AI parking direction in pull-through spots (not changed by the wind direction or active runway) 12) Force Runway in use. Example, taxi all the way to runway xx instead of taking the nearest one.

[REPORTED]Game crash on switching to isometric view in CA Happened while I was switching to isometric view "3rd person", while in an Avenger unit. Also, upon the crash and display of the error window "Unfortunately DCS has stopped..." it is impossible to click on anything or hit enter to send the crash report. Actually hitting ESC seems to maybe make it progress, but unsure what happened on the next step when I hit ESC again (prompt went away).

With the renewed interest into the Ka-50 with the upgrade model coming, I wanted to put the suggestion out for modifying the ABRIS which currently shows all threats in a mission. Surely it is not the intention of ED to simulate a "god's eye view" of all threats on the battlefield. As it stands, when playing on a multiplayer server the Ka-50 has become a bit of a cheat. Need to know what kind of threats remain, even down to the smallest AAA unit, or MANPAD? Put electric power on, turn on ABRIS, mark coordinates. It's pretty cheat-y. Suggestion for a more elegant implementation: - Only allow classification of larger, less mobile sams to show on the abris. Highly mobile units that are hidden in towns or trees should not be shown to the player. - Allow the option via mission editor to display the unit on the ABRIS, or as I believe is done in the Hornet, units marked as visible are the only ones to show on the F-18 SA page. I hope some consideration is given to what I think is the most game breaking issue for multiplayer in the Ka50.

No. Last info from HB guys earlier on this thread that I saw is that they are having a hard time reproducing it. Happened to a squadmate 3x last night on BFPG server, so it can't be that difficult if they'd play there a few sorties. Also getting quite a few CTD on that server as well in the Tomcat.

Telling Jester to scan even Mid-Low points the radar down 16 degrees, which even at the lowest distance (25nm) it gives you a 0 to 0 elevation scan pattern. Suggest modifying the elevation levels to something more moderate, like 2-5 degrees on the mid-low and maybe 7-10 on the low/high setting. Being able to input a custom setting would be bonus! For example, jester scan 3° high, or 6° low.

Me and my squad mates getting this a few times over the last couple days. Server is BF PG if that helps narrow it down at all.

The problem lies in the way DCS handles the transition from night to day. If you want to see it, put it on a full moon night, about an hour before sunrise, and time accelerate it. You will have lovely moon lighting that fades to a pitch black night just before the sunrise sequence starts. It is a fundamental lighting issue that ED needs to resolve.

I've gone ahead and done my beta tester thing and found the problem relates specifically to Parking spot J11 and J12 for anything wider than an F-5 or Mig-21 (shortest wingspan I could think of). Measuring on the F10 map shows those walls are 49 feet from the hangar, where most of the other ones are 65. https://streamable.com/brdz2

Just experienced the same thing. Mine was a Mig29.

Fixed as of today's patch. Thank you! Was my biggest irritation on the map. Now if we can just do something about these blasted static tankers that keep trying to smash into the Stennis.

Basically as the title says. The trigger for SCENERY REMOVE OBJECTS does not sync to clients, only the host of a multiplayer mission. While this provides a nice tool for mission makers, it is pointless in a MP environment. One example of a very handy use of this trigger is to remove the static oil tankers in PG that seem to have problems running into the carrier. Pointless, if only the host can see the action though.

I understand your requests but I think having the R77 is an adequate balance for the 54's. The ROE in place will likely (if they are smart) restrict the F-14 pilots from carrying a full load of 54s. I really don't envision them lobbing 6 54s at targets since they will not be allowed to engage on the other side of the river. I'm not adding any additional modules for this round. If there is enough participation, perhaps modifications for the next round. As it is, the scenario was designed primarily as F-5 vs Mig 21, with emphasis on helicopter work, and as of now, there are 0 F-5 or helicopters signed up.

There arent standard limitations to Fox 3 if that's what you are asking. R77 and 54s will be in place. With unlimited numbers. However, the rearming of fox 3 will be 100nm away from the front line, so if you're willing to take a 200nm round trip for more, then be my guest. Also, beware of the special ROE in place. If you shoot fox 3 across the border for a kill, you are losing your team massive points.