DCS Features Wish List

[diveplane]

plz update the ship wake

[Maraudeur]

I don't know if this issue is ok for this thread:music_whistling:, but would it be possible to have the apron position of the aircrafts aligned with the ground marks (or the countrary)?

This way this would prevent a deadly spawning or respawing on someone parked at the apron:doh:, for we can now choose the parking position (that is a great improvement, thanks for it ED :thumbup:)

[Frogisis]

I would like to be able to request a mark from the JTAC. Not sure how the mark is determined now, if it's random or what, but I just did a night mission where a single "package" of armored targets was spread over about a dozen square miles, with just some coordinates radioed to me in the center. For the first tank, the JTAC used the IR pointer, but each time after that it was just "re-attack is authorized" and I had to fly around and around and around looking for each isolated unit with no further coordinates despite my requests, and it didn't strike me as challenging so much as inelegant and wasteful. Much in the same way you can ask JTAC to repeat the brief, it'd be nice if you could ask them to mark it again if they have that capability active in the first place. Maybe there could be some kind of catch, like if they light up too many things they give away their position and are no longer an invisible unit.

 

Also still pining for an in-flight music option/directory a la IL-2. The feels!

Edited December 1, 2012 by Frogisis

[Home Fries]

For multiplayer, the ability to input direct IP using a DNS address (for those of us with dynamic IPs).

 

Also, default to 10308 on Direct IP if a port is not indicated, rather than require a port to be entered following the IP. This still allows people to use custom ports (just put the custom port in after the IP), but will make things easier for those of us who are less TCP/IP savvy.

[Teknetinium]

I wish there will be TWS for mig-29S, And I wish that it would be possible to convert it to Su-27, I know it is unrealistic but we could pretend as it is early upgrade, it would be more realistic then Su-27S usage of R-77 in FC2 servers.

[Kuky]

let's not wish for things that aren't realistic, maybe wish for target step functionality?

[Cali]

I wish for more functions with the F-15, since it's missing stuff that should be there. I just really want features and functions that are missing from all aircraft. As long as there is supported documents stating what the aircraft has.

[-Demon-]

Payload and Skin preview

 

Hi all,

 

I just saw that thread here and started to read. But then I saw the first entry is back from 2008. So honestly I didnt read throuogh the whole post and just want to add that feature to the wish list.

 

In LO:MAC there we had a weapon preview and skin preview in a small window in the mission editor. Why did we lose that? I have very limited time to fly and I also only know the basics of weapons and armament so I would find it very handy, to actually see the weapon I select for my mission with a short infotext on what it does. I find it very inconvinient to swap to the enzyclopedia, to look for the corresponding site to look up everything. And very often I can't even find what I am looking for. Maybe a direct link from the weapon select page to the enzyclopedia could do the trick as well.

 

Another thing which bothers me is that I have NO CLUE how the diferent liveries look like. Yes, I could go into the folder and look at it with an external picture viewer. But why not opening a small window with the selected airplane showing plus the selected liverie? That would make it so much easier to configuere it to your desire.

 

In short:

 

- aircraft model preview mode for realtime preview of liveries and weapons

- in weapon select mode a link to the coresponding missile, bomb, pod what so ever to see the main infos and also for beginners to see the effectivness of the bomb without reading through the enzyclopedia.

 

Thats all for now and I am wondering if anyone out there is interested in that as well. I guess not all of the buddies here are real pilots and jobless people who spend hours of reading and getting into each weapon :smartass:

 

Thanks for letting me know what you think about that feature which we once had in old times :)

 

best regards and always check your six!

 

Demon

[sobek]

In LO:MAC there we had a weapon preview and skin preview in a small window in the mission editor. Why did we lose that?

 

With ongoing development, the simulator engine needed more and more RAM, up to a point where the GUI and the engine together neded more RAM than a 32bit operating system could allocate. Since 64bit OSs were still quite uncommon at that point, it was decided to split the GUI into a separate executable and only start the simulation engine when the GUI is not needed. That is the reason why in-engine-renders of weapons, aircraft etc are currently not possible.

 

With the widespread use of 64bit systems and people installing tons of RAM, ED might merge the GUI with the engine again, but it is a matter of time and ressources available.

 

Edit: Btw. you don't need to read the 200+ pages of this thread if you want to know whether something has been covered, searching for a few keywords instead would have sufficed.

 

regards

[-Demon-]

@sobek

 

yes you are completly right about that search thing. Will consider that the next time. But thanx anyway that you took the time to reply that quickly.

 

Do you have a trick how to get a quicker overview of the weapons with having to study? Maybe there is something I missed in the enzyclopedia?

Any comment will be appriciated :)

 

I just need to say: this is a damn fine cool community!

 

Cheers

 

Demon

[sobek]

Do you have a trick how to get a quicker overview of the weapons with having to study?

 

No, unfortunately not. The rearming system in game and in the GUI both require you to be familiar with the weapons you are choosing.

[-Demon-]

well too bad...but thanks for taking the time Sobek!

[D4n]

You just have the encyclopedia in the DCS menu, read the "weapons" tab through and learn by heart! ;) :)

 

Then by Alt + Ä you can see/check in flight what weapons u got on which stations... (and on parking place to reload)

[-Demon-]

You just have the encyclopedia in the DCS menu, read the "weapons" tab through and learn by heart! ;) :)

 

Then by Alt + Ä you can see/check in flight what weapons u got on which stations... (and on parking place to reload)

 

will check that...thanks :)

 

cheers

 

Demon

[Home Fries]

One suggestion for multiplayer and skins:

 

DCS World doesn't download skins on the fly, and given the size of skins this is completely understandable.

 

Right now as I understand it, If client #1 does not have the skin of client #2, then client #1 will use the first skin available. Since I'm sure plenty of people like to use personalized versions of default skins (e.g. adding their pilot name under the canopy of the default skins), it would be great to have DCS World assign a proper substitute that could be defined in the definition.lua.

 

For example, If I decide to use the 19th FS (AK)-Home Fries skin for the F-15C (the default AK skin with my name on the jet and flightsuit), I would like to be able to add something like this to the definition.lua:

{alias="19th FS (AK)"};

which would point to the default AK skin.

 

This way, people who don't care about my personalization would at least see that I was flying with the 19th in an online session.

 

The ideal implementation would be a concatenated substitution, in which you could list multiple aliases and DCS World would try to apply them in order, so if you personalized a 3rd party skin (e.g. 19th FS Mod Eagle), then you could have

{alias="19th FS Mod Eagle (AK)"};
{alias="19th FS (AK)"};

This way, DCS World would look for the original Mod Eagle skin, then if the client didn't have that it would check down to the 19th FS default skin.

 

EDIT: For the record, I'm not a LUA programmer. The code entries are pseudocode only and are implementation designs, not execution.

Edited December 6, 2012 by Home Fries

[Teknetinium]

I wish for more functions with the F-15, since it's missing stuff that should be there. I just really want features and functions that are missing from all aircraft. As long as there is supported documents stating what the aircraft has.

 

 

AIM-120C was carried on later F-15 versions then in FC3 F-15:), FC is very blurry when it concern version of aircraft and systems on it, if you have been flying online in FC2 you probably know that it is like Standard to use R-77 on Su-27, 51st server didn't allow it, I'm all up for realism, but if TWS would be implemented in MIG-29 it would be more realistic for Su-27 use R-77 whit TWS .

 

DCS is great, patiently waiting for DCS fighter, I can tell you that I know basic operations in A-10 C, P-51D and ka-50 (Boring for me who wait for something faster).

MIG-31 would be very interesting to chase F-15E in ;)

 

FC3 Wishlist:

1. TTI timer on Russian HUD

2. TWS for MIG-29S

3. INS for missiles

4. Damaged aircraft cant shoot/better missile warhead damage (No more burning aircraft spamming and killing stuff on the battlefield)

5. Better models for both exterior and cockpit (Su-27/33, MIG-29)

 

+ the bugg list:( ( wish you best luck ED)

Edited December 7, 2012 by Teknetinium

[Cali]

AIM-120C was carried on later F-15 versions then in FC3 F-15:), FC is very blurry when it concern version of aircraft and systems on it, if you have been flying online in FC2 you probably know that it is like Standard to use R-77 on Su-27, 51st server didn't allow it, I'm all up for realism, but if TWS would be implemented in MIG-29 it would be more realistic for Su-27 use R-77 whit TWS .

 

DCS is great, patiently waiting for DCS fighter, I can tell you that I know basic operations in A-10 C, P-51D and ka-50 (Boring for me who wait for something faster).

MIG-31 would be very interesting to chase F-15E in ;)

 

FC3 Wishlist:

1. TTI timer on Russian HUD

2. TWS for MIG-29S

3. INS for missiles

4. Damaged aircraft cant shoot/better missile warhead damage (No more burning aircraft spamming and killing stuff on the battlefield)

5. Better models for both exterior and cockpit (Su-27/33, MIG-29)

 

+ the bugg list:( ( wish you best luck ED)

 

I know the Su-27/R77 was popular on servers and it was nice seeing that you guys kept it real. I don't care what aircraft gets improvements, we all want them to be like the real thing. If there is proof that this jet can do this or that.....I'm all for it no matter if it's a Su-27, F-15, Mig-29 or whatever. As long as there is proof that and not just from a few internet sites, I'm good with that.

 

Like you, a lot of people are waiting for DCS fighters, which will take a long time before we are at the FC level. I foresee a lot of people being mad, threads created about why do we have this and not that. I hope you don't think I'm against you when I respond to your post. I just want realism......for both sides, no fairy tales here. We have a long way to go.

[-Demon-]

One suggestion for multiplayer and skins:

 

DCS World doesn't download skins on the fly, and given the size of skins this is completely understandable.

 

 

Why not implement a pop up which asks the player if he wants to download a skin? Well, on the other hand if 32 players are using all unique skins that could be a bit of a problem. But than again, the user could select the one he wants to download? Just my thoughts, not really thought till the end maybe :music_whistling:

 

Cheers

 

Demon

[falcon_120]

I would like visible contrails for planes that are known to have it,for example the mig 29 and his smoky engines,also the rest of the aircrafts in some regimes like when they go from very low r.p.m to full throttle.

[Grimes]

Why not implement a pop up which asks the player if he wants to download a skin? Well, on the other hand if 32 players are using all unique skins that could be a bit of a problem. But than again, the user could select the one he wants to download? Just my thoughts, not really thought till the end maybe :music_whistling:

 

Usually you have to reload the sim in order for changes or new files to be "valid" within the sim world. However it is a neat idea, especially if the files could be hosted on an additional server rather than the game server.

[-Demon-]

Usually you have to reload the sim in order for changes or new files to be "valid" within the sim world. However it is a neat idea, especially if the files could be hosted on an additional server rather than the game server.

 

hmm, than it should be a routine, which checks upfront if the a skindownload is needed. Then you can choose to download the skin, which will be installed automatically and then the server starts to load with the new skin? I have no clue if that could be easyly achieved.:huh:

 

Cheers

 

Demon

[Cali]

I would like visible contrails for planes that are known to have it,for example the mig 29 and his smoky engines,also the rest of the aircrafts in some regimes like when they go from very low r.p.m to full throttle.

 

How about contrails that start and stop at different altitudes would be a nice starter.

[Home Fries]

Usually you have to reload the sim in order for changes or new files to be "valid" within the sim world. However it is a neat idea, especially if the files could be hosted on an additional server rather than the game server.

 

Given that some skins are about 40Mb in size, the additional server would be the only reasonable alternative. Even if you had the option to download the skins before you entered the game, you would be eating too much of the skin owner's upload speed, and would force lag on their part if they were in game.

 

Now if you would want to go all in to implement a dynamic download, there are a couple of options that could be used independently or in combination..

 

1. have an entry in the description.lua that provides a link to the skin itself. This creates a chicken-egg issue, as most download links are not known until the file itself is uploaded, but such a thing could be managed by site admins. Then when prompted to download the skin from in-game the client would be sent to the link for downloading the file.
   
2. When dealing with personalized skins using decol and patch files (not full-blown personal skins), have a standard naming convention in the Liveries folder that tells DCS that it is a personalized spin-off of an existing skin. Something like <skin name>_|_<callsign> could let DCS know that the files in this folder are tied to the original <skin name>, and "true" settings in description.lua would look in the original <skin name> folder as well as the path. Then the <callsign> could be tied to the pilot profile or multiplayer callsign so that this personalized variant would show up by default in-game. This way you could automatically have your aircraft personalized as a client even if the server's mission slotted a default or generic 3rd party skin. The patch and decol files are fairly small (tgas converted to DDS), so they alone wouldn't cause a major hit on the uploader.
   

 

 

Of course, these options (esp. the second option) would require significant re-coding to implement. It would probably be easier to implement my "alias" option and allow clients to choose their own skin in a multiplayer session. Personally, I would love to see all 3 implemented in combination.

Edited December 7, 2012 by Home Fries

[FubarBundy]

save game facility

 

I think it would be useful to be able to save the game status occassionally. This way a branching campaign could be constructed from mission events. It would also help in the event of MP server crash etc as game could be restarted from last position.

[gregzagk]

I think it would be useful to be able to save the game status occassionally. This way a branching campaign could be constructed from mission events. It would also help in the event of MP server crash etc as game could be restarted from last position.

 

This feature together with the last Combined arms updates that have been announced would solve a lot of problems ! Lets hope ED will move forward this one :)