Boagord

The translation : In the mission editor, the F-15E has mysteriously disappeared. I can no longer locate the F-15E in my mission editor. However, the command files are still present, as well as the theme. I've deleted DCS and then reinstalled it. Nothing. I've performed the repair three times. Nothing. I've uninstalled and reinstalled the F-15 four times. Nothing. I'm at a loss, I don't know what else to do. Ma réponse : Est-ce que ça ne serait pas la date de la mission qui poserait problème? Selon les réglage et l'année de la mission le F15E peut ne pas être dispo. Je suis sur Discord si besoin. My Answer : Wouldn't it be the mission date causing the issue? Depending on the settings and the year of the mission, the F-15E may not be available. I'm on Discord if needed.

After some tests, the fuel flow of a clean aircraft is spot on, but it seems that the drag caused by the stores is a tiny fraction of what it should be: In the documentation, the relationship between the DI (Drag Index) and the fuel flow appears to be of the form ax + B For example, for 50,000 lbs, 520 KTAS, and 10,000 ft, the relationship appears to be close to: 10518 + DI x 73.875 A clean F15-E has a 21,3 DI and the FF is very close to the documented one but the coefficient of the variable linking the FF and the DI appears to be close to 74 in the documentation and 13 in the measurements taken in DCS. null Although I cannot validate all of this as I don't have enough time, I am certain there is an issue somewhere because in no configuration can I achieve a fuel flow requirement exceeding 15,000 lbs/hour for 60,000 lbs, 520 KTAS, and 10,000 ft, whereas I am supposed to have this result between 60 and 80 on the DI.

Temperature is calculated for 15° at SL, and standard as indicated in the PDF. I don't remember my setting in the ME. DI calculation is inside the spoiler, but As you said there is a huge difference. I did not yet test with a clean aircraft, I lack of time. If you want to try

So, here is the @crazyduncwork : https://github.com/crazydunc/F-15E-Strike-Eagle-Performance-Calculator/releases/tag/1.0.0.9 In the attached file there is my XLS. My xls is less precise than his .exe because I am far less experimented, I haven't yet integrated the pylons, and some conditional DIs like those of the 610 gal fuel tank but perhaps more transparent in understanding how it operates. The source of the work is a file F-15E-Flight-Manual-15-April-1993.pdf that can be found on Google (I'm not sure if I'm allowed to share it here). The fuel flow tables were taken from page 704 and the subsequent pages of this PDF. The DIs table was made from pages 625 and the following ones. As an exemple this loadout give a weight of ~80 000 lbs and a DI of 100: Since the gross weight is 80,000, pages 722-723 should be used, and on this page, the column corresponding to a DI of 100. This give : Do you observe the same flow rates? Is the documentary method correct? I hope my explanations are clear. fuel_consumption.xlsx

@crazydunc and I have developed an aircraft Drag Index and weight calculation system independently. A .exe and an XLS respectively. Then we have collaborated on the data extraction about the fuel flow, as noted in Appendix B (-229 engines) of the F-15E-Flight-Manual (15-April-1993) Currently, there is a significant discrepancy between the document (which applies well to the engines 229) and what is observed in DCS . Is this issue known? If not, we can provide specific figures or exemples.

The symbols (WP, MP, TGT etc.) are always too close to the center of the image. Or the image is too large in scale.When you want to designate a coordinate, if the target is not in the center of the image the coordinate is not the right one. Furthermore, to see the shift, simply take a vehicle visible to the radar, put a markpoint on the radar return spot and move the patch map. the markmoint and the target will not always be superimposed Some exemples : I'm going to play with 1.3: Now it is centered on the spot, but it is the TGT 2 which is offset: And now that I have moved the view, the square is still shifted towards the center but the shift is oriented towards the south (left) whereas on the first image it was rather towards the north (right) Still towards the center of the screen: So if we want to make a pinpoint the target must be in the center, you cannot marpoint several targets precisely in one frozen frame.

the bug still seems to be present

Have you any source about it? In DCS I can guide aim-7m in P-STT lock, so I assume it is a CW guidance. And I found this : https://books.google.fr/books?id=o3PTEuaoSosC&pg=PA1409&dq=aim-7m+cw+or+pulse&hl=fr&newbks=1&newbks_redir=1&sa=X&ved=2ahUKEwjPyNC4t7_xAhXQ3YUKHf5eAQoQ6AEwAnoECAkQAg

When in multiplayer as a client, if you are in a Viggen and a mark is created on the F10 map DCS will crash to desktop. Same thing happen with the F14 and asking jester to set a steerpoint from map. The hosting player do not crash. No problem with single player missions

Bump! the clock shifts approximately 13 seconds every 20 minutes, tested with the cold start instant action mission. I don't know if it's the same bug or another one.

We are using this script since a while now, it works great! Is it possible to add a border system? IE : Sam will engage intruders only ( Opposite force inside a zone) If some unit has been hit there is no more border It's just an idea

Same here. Need to wait a Hotfix?

Same problem here! Bump!

NAVAIR 01-F14AAP-1 : 2-173

I guess this clock http://www.heatblur.se/F-14Manual/cockpit.html#clock http://www.heatblur.se/F-14Manual/cockpit.html#rclock

Thanks for the answer. My point was to play this campaign with four players : 2 pilots and 2 rio. I have downloaded and edited the mission to have two planes as client. Next we found the issue, I redownload the campagn and extract the 8 missions to the savedgame directory. I opened the 3rd mission with the editor and I have the same issue: The mission 2, 3 4 and 7 have the same very short briefing : Clear the way for the strike package. Edit : I found the issue: My game is in french, and the issue is the localisation of the mission. If you set the game in french language you will find the issue I have. It is like if your long briefing was translated with my short one. Edit 2 : You have the issue with all other languages than english. The quickest way to correct it is to erase all the localisations other than english.

As you can see on tacview, it was a constant attitude climb. The key is to avoid to fall subsonic. On a lot of plane, M0.9 is the optimal climbrate, but here, it climbs better at around M1.2 It is only my personnal experience.

Oh! Another useless thread I created! :D

Hello, In MP there is some bad synch between Pilot and RIO : The pilot can see the inputs of the RIO (on TID) whe the RIO is typing but when the RIO press enter: ALT, RNG and BRG remains at 000 from the pilot's point of view. From the RIO point of view there is nothing wrong. When the pilot designates the IP visually on the HUD, as there is no offset from his point of view, the target is merged with the IP. I am using this : http://www.heatblur.se/F-14Manual/weapons.html#computer-initial-point I've tried several times, as a pilot and as a RIO and I am able to use the "Computer Initial Point" effectively in SP with no problem.

Thanks for the answers, I cannot add [No Bug] to the thread's Tittle. What shall I do ?

Yes, I agree it is a game. And more over a not so stable game. If your DCS or a wingman DCS crash you have to coldstart again. Which is a waste of time. Envoyé de mon SM-G930F en utilisant Tapatalk

I tried the first three missions with some friends, Pilot and Rio First one: A nice one, but a bit rought in the air, a lot of aircrafts. Second : Very well, nothing to say, a real pleasure! third : Nice but there is no briefing, and the voice doesn't correspond to the text, we had to relisten the .ogg to understand the push time @ 1614

Hello there, If you are goint supersonic (ie M1.2) you can go very high (too high). I was able to reach angel 90 the first time ( ran out of fuel) and 100 the second time ( stall). Tacview : https://cdn.discordapp.com/attachments/527941690540032010/576772963257286669/Tacview-20190511-153512-DCS.zip.acmi

So it's not a bug but a feature! If I understand, Case 1 above the sea should be done with the pneumatic altimer. Envoyé de mon SM-G930F en utilisant Tapatalk

In my cockpit, when I am above the sea, the radar altimeter point an altitude under the "F2" altitude. Is it normal? With a good QFE set, my pneumatic altimeter works well.