SgtPappy
-
Posts
1219 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Posts posted by SgtPappy
-
-
Great article.
On the F-15, I read him say that it took near-perfect execution, and that he came out roughly even at the end of his career. Awesome.
And guess what? I am not going to call him a liar or ask him to provide some data because his experience doesn't match with someone else's! Yay.
This is how easy these discussions should be! :joystick:
I can see both positions on this topic and how we always get a little heated because we're all nerds!
And even though I do agree with your assessments, I do not think Hummingbird explicitly stated anyone was lying, but rather implied that the assertion by the Eagle pilot did not line up with the data. Hummingbird and I are quite academic/engineer-oriented when it comes to data and data does not lie, so we often forget to look at other things when we see nice graphs :)
But as you also mentioned Steve, most planes in service aren't brand new with shiny engines and therefore do not fit the data well always.
-
The crew on the FFP were both B crew members. Its worth mentioning that all F-14B pilots do their initial FAM flights in the F-14A - so even a pilot who spends his entire career on the B will put 60-80 hours on the F-14A. The only Tomcat crews who have no flight time in the F-14A are F-14D crews.
So neither of those guys had experienced a real stall, but remembered the standard NATOPS restrictions and procedures - it left quite an impression, but reality was quite different. The TF30 was very stable at zone 5 and mil-power, even to 50+ deg of AOA. The issue is if you weren't at mil-power/zone 5 or if you decided to change power settings above 17-20 units of AOA. Then you could end up with problems, but it was actually pretty unpredictable. Usually things would work out fine, but every so often they wouldn't......and that would leave quite an impression as well.
-Nick
Do you mean that if you were just puttering about at lower than MIL power, the engine could randomly stall? Even if you didn't touch the power, the engine could just stall or would you have to pull AoA?
What if you level out, change power and then pull AoA before the RPM stabilized at the power setting you requested? Would that cause a stall?
Sounds like it took lots of skill and luck to be proficient in an F-14A.
-
That was not "the" reason, there were several reasons for Iran choosing the F-14, and one of them included that Iranian test pilots found the F-14A superior to the F-15A in mock fights that were later not allowed.
Earlier match ups had already alluded to this:
Wow awesome info! I have never seen that newspaper clipping before.
-
Possibly but he instructed at Top gun 86-89 and we had a mutual friend from the F3 so I believe him. The D was a different kettle of fish as you say. I do tend to think we look back on our previous types through rose coloured glasses. I shot an F15 from a neutral merge once in bfm but it was a bit of a one off ( tho it's always the fight I quote) and tend to forget the times he just out rated me for a quick kill.
Hence my last comment that in most cases its somewhat academic. I wouldn't enter a fight with a gen 4 fighter without advantage.
Sent from my ONEPLUS A6013 using Tapatalk
I don't think he's necessarily wrong, or a bad pilot - but if he got beat, at the end of the day, he was facing a better pilot.
The F-14A and moreso F-14B/D are probably very, very close in performance to the likes of the F-14A/C, F-16C B.30/B.50, F/A-18 and the small differences can give huge impressions during a knife fight!
-
That poor F/A-18 pilot would have had about 4 seconds of F-14 spike on RWR then soon after less than 5 seconds of pitbull.
Didn't even support the missile. Felt like a cheep kill. :joystick: The only time we ever get shot down is when we play around and purposely put ourselves in unnecessary danger.
In real life, the AWG-9 has to support the missile until a certain distance, then the AWG-9 commands the AIM-54 to turn on its terminal guidance seeker head after which point the F-14 can turn cold/go nose cold. This is one big limitation that DCS cannot simulate apparently due to the current engine.
-
Do we have any local F-14 crew members who can comment more on the RWR systems?
I wonder if the Gulf of Sidra incident F-14's could detect the MiG-23 radars.
-
https://www.upi.com/Archives/1987/04/29/Navy-using-fuzz-buster-radar-warning-devices/2670546667200/
I presume those were used because of newer SAM threats (like, newer than SA-2/3/6) showing up in the '80s?
Yes, that could certainly be in an issue. And I would not blame the system or its designers for this since newer SAMs had to be programmed in and could not be as easily added to the system database as easily as I would presume it was by the time of the Gulf War.
It would still be nice to hear what other limitations/capabilities a RIO would have when concerning the RWR. Perhaps I will have to wait for the F-14A!
Yep, there's a funny story about that. I know the A-6 in the early to mid 80's was equipped with an 'urgent' update to detect continuous-wave emitters (SA-6). It was a very basic detection system fitted to the glare shield. Two indicators (also fitted to the glare shield), one for the pilot and one for the B/N consisted of a set of 2 lights (green and amber), signalling whether the threat was on the plane's left or right side.This is how I understood it for the F-14's as well. Rudimentary indeed - which is why I have doubts about the RWR design.
-
Hi SgtPappy
I'm not so sure that the ALR-45/50 was an unreliable system, particularly for the time period in which was developed. From the reddit posts by TomcatRIO, I get the impression he was referring to the ALQ-100 rather than the ALR-45/50.:dunno:
He states that: "To be perfectly honest with you I do not remember the details. All i can tell you is we regularly experienced JEM, a jamming strobe on the TID created by jet engine modulation. This is what is reflected back to the AWG-9 when the radar signal hits the fan or turbine blades of the bogey aircraft engine. We did not train that much on the ECM aspects of things. The ALQ and warning systems were old and unreliable. In fact I seem to remember being instructed not to use the counter measure equipment as it acted as a homing beacon for certain SAMS. Nice huh."
There was also someone here whose father said the RWRs were useless to the point that they had to mount their own in the cockpit facing different directions.
-
AN/AlR45 is one of the first digital RWR systems succeeding the earlier analong AN/APR25/26 and 36 systems. its first was being introduced in 1970- 1974 meaning whilst the Vietnam war was still going on
https://www.aef.se/Avionik/Artiklar/Motmedel/Nya_hotbilder/RadarWarnStory.pdf
Sure the F15's AN/ALR56 also wasn't perfect, but that F15C in DCS had modernized version of it ( AN/ALR56M or something)
So all in all its not surprising that compared to the AN/ALR67 of the F14B it is less reliable and simpler system/
Thanks for the link, I have that document saved to my HDD already :) It's a pretty good overview of the evolution of the systems.
Although the ALR-45 was entering service while the Vietnam War was going on, the US left before any of their planes fought with that system for sure. The latest Rivet Haste F-4E's had the ALR-36/37 and from the google discussions between F-4 crews and ground crew, it seemed like it was much better than the earlier systems which Robin Olds hated.
I only imagine the ALR-45/50 was better but it's hard to tell. Not a lot of info out there other than what the crew says. It seems it would be nice if many crews could paint that picture for us.
-
Indeed, the F-14B has the ALR-67, but I am mostly curious about the F-14A (as it was the one that saw most combat in the 80's).
I would like an idea as to how bad/good RWRs of the time were, and if the were actually an improvement over the Vietnam-era ones mounted in F-4's, for example.
-
I was reading a few threads on here about the RWR of the F-14, primarily this one: https://forums.eagle.ru/showthread.php?t=140336
As well as a reddit F-14A RIO AMA: https://www.reddit.com/r/hoggit/comments/6w6nmo/f14a_rio_ama/
And it appears that the ALR-45/50 was a very unreliable system. My question is whether such unreliability was typical of the time. Are RWRs IRL this bad? I have read briefly that the ALR-56 that initially equipped the F-15 had reliability and false alarm problems as well. I suppose we are spoiled in DCS.
Furthermore, does anyone have anymore information or actual experience with these systems? My research shows that by 1977, the ALR-45C was fitted to F-14A's (see the Standard Aircraft Characteristics sheets: http://www.alternatewars.com/SAC/F-14A_Tomcat_SAC_-_April_1977.pdf) but I cannot find any information on this version of the ALR-45.
If any one of our community F-14 crews can clarify any ways to interpret or properly find ways to use this system, I would like to know!
Thank you!
-
I thought that if launched in STT, the Phoenix will still go pitbull like in TWS its just that using STT gives it a bit longer range. This isn't the case then?
I can't seem to find the thread I last read but this is not the case. According to what I've read, the devs have stated - and maybe they can chime in on this themselves - that the current limitations in the DCS engine do not support true AIM-54 limitations.
Apparently, if not commanded by the AWG-9, it will NOT go pitbull. Sorry everyone, wish I could find the thread but I am having trouble sifting through the search results.
-
Does anyone have good tacview tracks of defeating well-fired AIM-54s?
My friends and I have been doing a lot of F-14 and F-15 DACT recently and we've got to the point where we can notch AIM-54A mk60s launched from ~6000' and 15 nm, another launched at 6-8 nm from a similar altitude but the third one always seems to be the killer if fired between 3-5 nm.
It is close enough that it has lots of energy but also far away enough that unless you're beaming going Mach 0.9, it can still turn and hit. Maybe there's a way of maneuvering I am missing that could shake this large missile at that range?
I cannot upload my own tacviews now as I am at work. But if needed, I can do so on the weekend.
-
F14B RIO inputs section?
Oh really? Perhaps I did not look hard enough.
I had assumed views were universal :lol:
-
Is this the same issue that is causing my bindings to work only in the front cockpit but not the back?
I was doing my best to bind my views and zoom controls to the T16000 HOTAS set as usual, but I noticed that the hat switch, center view button and zoom controls only work from the front and do not respond in the back.
Furthermore, I usually bind head translation controls to the keypad but even those keyboard bindings do not function from the rear seat.
-
I was on the Cold War Server the other day and the mission was restricted to certain weapons - no R-60M, R-3R or AIM-9P5. I was fighting against a MiG-21bis and noticed that he fired a missile while I was about 90 degrees relative to his flight path (I was in burner the whole time).
From what I gather, there should have been no tone to begin with, and even if there was, it should have gone stupid sometime while I was turning. Is this an error or does the standard R-60 have a limited all-aspect capability? Or perhaps the missiles can track head on even while I am in afterburner?
I was sure of the missiles we had that day, I would not get hit, yet this happened:
Album here:
-
The reason is quite simple. The airframe is relatively small, and RWR is not the only system which needs antennae to function :) Besides, the interferometers need to scan quite a broad spectrum at the expense of accuracy. You should see the RWR as an aid to point your radar or other sensors in the right direction so you could acquire the target and as an Early warning device. There are ways to use the Electronic Warfare suite in more advanced forms, but since it's classified, I can't say anything more. Sorry.
Thank you for the answer! Do you mean to say that more antennae would decrease accuracy? As I understand, you would have identical antennae and they would all be capable of receiving signals from the same bandwidth so you would not be increasing detectable bandwidth anyway from adding more of the same antenna. Did I misunderstand?
Depends on the equipment. For example one of the eagle's wing antennae is split so it can make some form of altitude determination. Not all aircraft have this.So I gather it's more of a practical thing rather than being physically impossible. I also thought to myself yesterday that the 4 antennae are the minimum number you need as you can easily bank 90 degrees and determine attitude from there.
-
While we're on the topic of warning equipment, why is it that there is no altitude indication (i.e. the transmitter is above or below you) for RWR's?
We have the ability to compare radar signal strength in between port and starboard, front and back but why is there no RWR pair for the top and bottom of the aircraft?
I have had no luck finding any mathematical derivation for the RWR sorting algorithm or any kind of article for this question online.
-
Issues noted with remedies:
- Your quite low on ram, I would up your pagefile some more 8gb ram + 24gb pagefile.
- Autoexec.cfg has a syntax error, correct or rename file to stop running for testing
- ATI Graphics card driver doesn't seem to be installed correctly, doesn't show a driver version (Not quite sure if this is normal or not), but would reload supplied one from AMD and not a windows default version, would install the VC++ package first as most graphics drivers need that to be going to install correctly or at all.
- Problem with the "MICROSOFT Visual C++ Redistributable Package", either missing of corrupt - reload or repair it. https://www.digitalcombatsimulator.com/en/support/faq/556/#1490800.
- Backup / rename your old "Saved Games folder" if you have one and let DCS start with a default set of configs for testing.
- Run DCS and see if helped or not.
- If working better, redo controls and other configs.
Log errors:
=== Log opened UTC 2018-10-27 03:37:19
2018-10-27 03:37:20.977 ERROR Lua::Config: load error Config/main.cfg:[string "C:\Users\aaron\Saved Games\DCS.openbeta\Config/autoexec.cfg"]:1: '<eof>' expected near 'end'.
2018-10-27 03:39:27.368 INFO DX11BACKEND: Driver Command Lists - 0
2018-10-27 03:39:27.368 INFO DX11BACKEND: NvAPI_Initialize Error:
2018-10-27 03:39:27.375 INFO DX11BACKEND: ATI Adapter (null)
2018-10-27 03:39:27.375 INFO DX11BACKEND: ATI Driver Version
2018-10-27 03:39:27.375 INFO DX11BACKEND: AGS Version 3.2.0
2018-10-27 03:39:52.488 INFO EDCORE: try to write dump information
2018-10-27 03:39:52.513 INFO EDCORE: # -------------- 20181027-033951 --------------
2018-10-27 03:39:52.560 INFO EDCORE: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
=== Log closed.
Regards, Ian.
Thanks, MadDog! I will try this on the weekend.
- Your quite low on ram, I would up your pagefile some more 8gb ram + 24gb pagefile.
-
This is the first time my game has crashed on startup. I tried restarting, reinstalling and repairing the game. Below is my log:
=== Log opened UTC 2018-10-27 03:37:19
2018-10-27 03:37:20.013 INFO DCS: Command line: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin/DCS.exe"
2018-10-27 03:37:20.013 INFO DCS: DCS/2.5.3.23225 (x86_64; Windows NT 10.0.17134)
2018-10-27 03:37:20.095 INFO DCS: Hwid: JSxsnX6GU7IlDbO58Hhww86yKcgq9ApbRK7Z0g
2018-10-27 03:37:20.095 INFO DCS: DCS revision: 143208
2018-10-27 03:37:20.095 INFO DCS: Renderer revision: 17706
2018-10-27 03:37:20.095 INFO DCS: Terrain revision: 17609
2018-10-27 03:37:20.095 INFO DCS: CPU cores: 4, threads: 8, System RAM: 8159 MB, Pagefile: 16863 MB
2018-10-27 03:37:20.426 INFO EDCORE: (dDispatcher)enterToState_:0
2018-10-27 03:37:20.977 ERROR Lua::Config: load error Config/main.cfg:[string "C:\Users\aaron\Saved Games\DCS.openbeta\Config/autoexec.cfg"]:1: '<eof>' expected near 'end'.
2018-10-27 03:37:20.977 INFO Dispatcher: 2018/10/26 23:37 V1803061700
2018-10-27 03:37:21.064 INFO INPUT: Device [Keyboard] created deviceId = -1
2018-10-27 03:37:21.065 INFO INPUT: Device [Logitech Extreme 3D {9C1CC860-4030-11e8-8001-444553540000}] created deviceId = -1
2018-10-27 03:37:21.065 INFO INPUT: Joystick created[Logitech Extreme 3D {9C1CC860-4030-11e8-8001-444553540000}], ForceFeedBack: no
2018-10-27 03:37:21.113 INFO INPUT: Device [Mouse] created deviceId = -1
2018-10-27 03:37:21.278 INFO SOUND: Using driver: xaudio29
2018-10-27 03:37:21.293 INFO SOUND: Found 4 available audio device(s):
2018-10-27 03:37:21.293 INFO SOUND: 0: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{68709b2e-f908-426b-bcd0-7bfcd294360f}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "Headphones (High Definition Audio Device)"
2018-10-27 03:37:21.293 INFO SOUND: 1: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{9595eb57-4b4e-432b-a64b-f46f620dfae2}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "Digital Audio (S/PDIF) (High Definition Audio Device)"
2018-10-27 03:37:21.293 INFO SOUND: 2: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{c9065658-5f6a-479d-8f20-65c2ef2bfff9}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "3 - E2250 (2- AMD High Definition Audio Device)"
2018-10-27 03:37:21.293 INFO SOUND: 3: ID: "\\?\SWD#MMDEVAPI#{0.0.0.00000000}.{11d4a981-e7bc-449f-b820-9e201494feab}#{e6327cad-dcec-4949-ae8a-991e976a79d2}", Name: "Digital Audio (S/PDIF) (High Definition Audio Device)"
2018-10-27 03:37:27.881 INFO SOUND: loaded 1312 sdefs from "sounds\sdef"
2018-10-27 03:38:00.736 INFO NET: Login success.
2018-10-27 03:38:01.671 INFO NET: Got auth data.
2018-10-27 03:38:01.885 INFO DCS: Successfully got authorization data.
2018-10-27 03:38:01.888 INFO DCS: Loading installed modules...
2018-10-27 03:38:05.708 INFO SECURITYCONTROL: Loaded (mm) mods/tech/wwii units/dcs_module.dll.crypt
2018-10-27 03:38:08.198 WARNING DCS: "./Mods/aircraft/FA-18C" is not authorized.
2018-10-27 03:38:10.776 WARNING DCS: "./Mods/aircraft/Su-33" is not authorized.
2018-10-27 03:38:13.623 WARNING DCS: "./Mods/terrains/PersianGulf" is not authorized.
2018-10-27 03:38:22.131 INFO Scripting: OBSOLETE mount_vfs_sound_path() used in ./CoreMods/aircraft/AJS37/entry.lua
2018-10-27 03:38:28.373 INFO Scripting: PLUGINS START-------------------------------------------------
2018-10-27 03:38:29.437 INFO SOUND: loaded 15 sdefs from ".\coremods\aircraft\av8bna\sounds\sdef"
2018-10-27 03:38:29.669 INFO SOUND: loaded 9 sdefs from ".\coremods\aircraft\c-101\sounds\sdef"
2018-10-27 03:38:29.839 INFO SOUND: loaded 12 sdefs from ".\coremods\aircraft\chinaassetpack\sounds\sdef"
2018-10-27 03:38:30.435 INFO SOUND: loaded 19 sdefs from ".\coremods\aircraft\m-2000c\sounds\sdef"
2018-10-27 03:38:30.527 INFO SOUND: loaded 10 sdefs from ".\coremods\aircraft\mig-21bis\sounds\sdef"
2018-10-27 03:38:30.673 INFO SOUND: loaded 2 sdefs from ".\coremods\aircraft\sa342\sounds\sdef"
2018-10-27 03:38:30.880 INFO SOUND: loaded 42 sdefs from ".\mods\tech\wwii units\sounds\sdef"
2018-10-27 03:38:32.500 INFO Scripting: LTAvehicle
2018-10-27 03:38:32.500 ERROR Scripting: <NULL>
2018-10-27 03:38:32.974 INFO SOUND: loaded 70 sdefs from ".\mods\aircraft\bf-109k-4\sounds\sdef"
2018-10-27 03:38:33.239 INFO SOUND: loaded 71 sdefs from ".\mods\aircraft\f-5e\sounds\sdef"
2018-10-27 03:38:33.462 INFO SOUND: loaded 53 sdefs from ".\mods\aircraft\f-86\sounds\sdef"
2018-10-27 03:38:33.506 WARNING DCS: Not Authorized, no registry path: ./Mods/aircraft/FA-18C
2018-10-27 03:38:33.506 INFO Scripting: plugin: SKIPPED 'F/A-18C': not authorized
2018-10-27 03:38:33.941 INFO SOUND: loaded 70 sdefs from ".\mods\aircraft\mig-21bis\sounds\sdef"
2018-10-27 03:38:34.282 INFO SOUND: loaded 72 sdefs from ".\mods\aircraft\mig-15bis\sounds\sdef"
2018-10-27 03:38:34.658 INFO SOUND: loaded 84 sdefs from ".\mods\aircraft\spitfirelfmkix\sounds\sdef"
2018-10-27 03:39:03.411 WARNING DCS: Not Authorized, user-skipped: ./Mods/aircraft/Su-33
2018-10-27 03:39:03.411 INFO Scripting: plugin: SKIPPED 'Su-33 Flanker by Eagle Dynamics': not authorized
2018-10-27 03:39:03.565 INFO SOUND: loaded 21 sdefs from ".\mods\aircraft\uh-1h\sounds\sdef"
2018-10-27 03:39:04.091 WARNING DCS: Not Authorized, user-skipped: ./Mods/terrains/PersianGulf
2018-10-27 03:39:04.091 INFO Scripting: plugin: SKIPPED 'PersianGulf': not authorized
2018-10-27 03:39:04.091 INFO Scripting: plugin: SKIPPED 'A-10A by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics'
2018-10-27 03:39:04.091 INFO Scripting: plugin: SKIPPED 'F-15C': disabled by 'Flaming Cliffs by Eagle Dynamics'
2018-10-27 03:39:04.092 INFO Scripting: plugin: SKIPPED 'MiG-29 Fulcrum by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics'
2018-10-27 03:39:04.092 INFO Scripting: plugin: SKIPPED 'Su-25A by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics'
2018-10-27 03:39:04.092 INFO Scripting: plugin: SKIPPED 'Su-27 Flanker by Eagle Dynamics': disabled by 'Flaming Cliffs by Eagle Dynamics'
2018-10-27 03:39:04.095 INFO Scripting: PLUGINS DONE--------------------------------------------------
2018-10-27 03:39:10.128 INFO SECURITYCONTROL: Loaded ./CoreMods/aircraft/AV8BNA/bin/AV8B_AI.dll
2018-10-27 03:39:10.132 INFO SECURITYCONTROL: Loaded ./CoreMods/services/CaptoGlove/bin/edCaptoGlove.dll
2018-10-27 03:39:11.288 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/A-10C/bin/A10.dll
2018-10-27 03:39:11.357 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/A-10C/bin/Cockpit_A10Common.dll
2018-10-27 03:39:11.450 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/A-10C/bin/Cockpit_A10C.dll
2018-10-27 03:39:12.671 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Bf-109K-4/bin/Bf109K4.dll
2018-10-27 03:39:14.238 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/F-5E/bin/F5E.dll
2018-10-27 03:39:16.051 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/F-86/bin/F86.dll
2018-10-27 03:39:18.174 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Flaming Cliffs/bin/FC3.dll
2018-10-27 03:39:18.254 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Flaming Cliffs/bin/A10A.dll
2018-10-27 03:39:18.342 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Flaming Cliffs/bin/F15.dll
2018-10-27 03:39:18.899 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Flaming Cliffs/bin/Su27.dll
2018-10-27 03:39:19.221 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Flaming Cliffs/bin/Su33.dll
2018-10-27 03:39:19.224 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Flaming Cliffs/bin/MiG29.dll
2018-10-27 03:39:20.680 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/MIG-21bis/bin/FlightModel.dll
2018-10-27 03:39:20.938 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/MIG-21bis/bin/Avionics.dll
2018-10-27 03:39:22.259 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/MiG-15bis/bin/Mig15.dll
2018-10-27 03:39:22.277 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/P-51D/bin/P51Base.dll
2018-10-27 03:39:24.437 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/P-51D/bin/P51B.dll
2018-10-27 03:39:24.629 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/P-51D/bin/Cockpit_P51Common.dll
2018-10-27 03:39:24.728 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/P-51D/bin/Cockpit_P51D.dll
2018-10-27 03:39:24.754 INFO SECURITYCONTROL: Loaded (mm) ./Mods/aircraft/SpitfireLFMkIX/bin/SpitfireLFMkIX.dll.crypt
2018-10-27 03:39:24.756 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/TF-51D/bin/P51Base.dll
2018-10-27 03:39:24.757 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/TF-51D/bin/TF51D.dll
2018-10-27 03:39:24.762 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/TF-51D/bin/Cockpit_P51Common.dll
2018-10-27 03:39:26.688 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Uh-1H/bin/Uh1H.dll
2018-10-27 03:39:26.778 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/Uh-1H/bin/CockpitUH1H.dll
2018-10-27 03:39:26.921 INFO SECURITYCONTROL: Loaded ./Mods/aircraft/jsAvionics/bin/jsAvionics.dll
2018-10-27 03:39:27.368 INFO DX11BACKEND: Driver Concurrent Creates - 1
2018-10-27 03:39:27.368 INFO DX11BACKEND: Driver Command Lists - 0
2018-10-27 03:39:27.368 INFO DX11BACKEND: NvAPI_Initialize Error:
2018-10-27 03:39:27.375 INFO DX11BACKEND: ATI Adapter (null)
2018-10-27 03:39:27.375 INFO DX11BACKEND: ATI Driver Version
2018-10-27 03:39:27.375 INFO DX11BACKEND: AGS Version 3.2.0
2018-10-27 03:39:27.375 INFO DX11BACKEND: TRUNK renderer init: showShaderError coreCount=1
2018-10-27 03:39:30.071 INFO DX11BACKEND: commonPool: 68-128, cbPool: 5-14, samplerPool: 5-16
2018-10-27 03:39:30.273 INFO DX11BACKEND: DX11ShaderBinaries::loadCache Bazar/shaders/fxo/fxo.zip
2018-10-27 03:39:40.692 INFO DX11BACKEND: DX11ShaderBinaries::loadCache done. Loaded 786/786.
2018-10-27 03:39:40.704 INFO DX11BACKEND: DX11ShaderBinaries::loadCache C:\Users\aaron\Saved Games\DCS.openbeta\fxo
2018-10-27 03:39:52.488 INFO EDCORE: try to write dump information
2018-10-27 03:39:52.513 INFO EDCORE: # -------------- 20181027-033951 --------------
2018-10-27 03:39:52.560 INFO EDCORE: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
2018-10-27 03:39:52.623 INFO EDCORE: # C0000006 IN_PAGE_ERROR at 4E35CC57 00:00000000
2018-10-27 03:39:52.662 INFO EDCORE: 00000000 00000000 0000:00000000
2018-10-27 03:39:52.826 INFO EDCORE: 4E35CC57 008FE370 0000:00000000 C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll memcpy()+287
2018-10-27 03:39:52.981 INFO EDCORE: 400A8FF1 008FE3A0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edCore.dll ?getName@MemBinaryFileR@io@@UEBAPEBDXZ()+61
2018-10-27 03:39:52.995 INFO EDCORE: 03CCE086 008FE4D0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll ?interframeResourceSync@DX11Renderer@RenderAPI@@UEAAX_N@Z()+5206
2018-10-27 03:39:52.996 INFO EDCORE: 03CCEB31 008FE710 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll ?interframeResourceSync@DX11Renderer@RenderAPI@@UEAAX_N@Z()+5CB1
2018-10-27 03:39:53.131 INFO EDCORE: 03CCE686 008FE7C0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll ?interframeResourceSync@DX11Renderer@RenderAPI@@UEAAX_N@Z()+5806
2018-10-27 03:39:53.264 INFO EDCORE: 3FC6B50E 008FE9C0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\GraphicsVista.dll ?initialize@Renderer@Graphics@@QEAA_NPEAXHHH@Z()+52E
2018-10-27 03:39:53.265 INFO EDCORE: 3333CFB0 008FEFD0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Visualizer.dll ?SetProjBounds@smCamera_Implement@@UEAAXPEBM@Z()+3100
2018-10-27 03:39:53.266 INFO EDCORE: 3334A424 008FF010 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\Visualizer.dll ?CreateSceneManager@smSceneManager@@SAXXZ()+24
2018-10-27 03:39:53.266 INFO EDCORE: 9D6BC64F 008FF340 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
2018-10-27 03:39:53.266 INFO EDCORE: 9D6BA439 008FF3C0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
2018-10-27 03:39:53.267 INFO EDCORE: 9D32A2D7 008FFBD0 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
2018-10-27 03:39:53.269 INFO EDCORE: 9D84E99F 008FFC10 0000:00000000 C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe
2018-10-27 03:39:53.271 INFO EDCORE: 6CBB3034 008FFC40 0000:00000000 C:\WINDOWS\System32\KERNEL32.DLL BaseThreadInitThunk()+14
2018-10-27 03:39:53.271 INFO EDCORE: 6D731461 008FFC90 0000:00000000 C:\WINDOWS\SYSTEM32\ntdll.dll RtlUserThreadStart()+21
2018-10-27 03:40:08.784 INFO EDCORE: Minidump created.
2018-10-27 03:40:08.973 INFO DCS: try to write track file
2018-10-27 03:40:08.975 INFO DCS: 'C:\Users\aaron\Saved Games\DCS.openbeta\Logs\dcs.20181027-033951.crash' deleted successfully
2018-10-27 03:40:09.054 INFO DCS: 'C:\Users\aaron\Saved Games\DCS.openbeta\Logs\dcs.20181027-033951.dmp' deleted successfully
2018-10-27 03:40:09.054 WARNING DCS: track file empty
2018-10-27 03:40:09.054 WARNING DCS: mission file empty
=== Log closed.
-
Did you check your ram usage? Not sure if 8GB is enough anymore. I had this similar issue a few weeks ago. Except I was at 12GB ram. Bumped myself up to 16GB - Runs a bit better, but only for a few days..lol Now It's maxing at 16GB - fishing around work for more ram now..
That is something I will have to check. Upgrading soon to an RX580 soon since I found one for cheap.
Thing is, I managed ONCE to fly in the Burning Skies server was dogfighting for a full sortie with no issue. The difference is I could hear my tower "spool up" - fans running high RPM which used to happen all the time.
Since the last update, the fans don't kick in 99% of the time and therefore DCS does not work. Is this RAM-related? Or something more sinister?
-
DCS has been a nightmare for me recently. It hangs at every screen if I try to join multiplayer - first at the menu only for about 1 minute, then if I join any server, the loading screen for 10 mins and then the splash screen for another 5 mins and then it either joins the server (rarely) at which point it freezes at the aircraft list indefinitely or it returns to the menu.
This did not happen last month when I played very little due to frame rate issues but today, I only managed to enter an aircraft once. At which point my screen froze indefinitely again.
Specs: windows 10 64 bit, intel® core i7-2600K CPU @ 3.4 GHz (8 CPUs), 8 GB of RAM, AMD radeon
-
Apologies if I'm coming off as overly pedantic, but the RM8A is a turbofan. On dry thrust it does indeed lose thrust with increasing airspeed, as you say, but with the afterburner engaged thrust is either more or less constant with airspeed (up to the transonic region, on low afterburner thrust settings) or increases with airspeed. At max zone 3 the thrust increase is almost - but not quite - linear with increasing airspeed from standstill to Mach 1.1 at sea level.
Here is the thread I was talking about, please refer to the thrust-to-drag diagrams therein if anything is unclear.
As far as I know most military afterburning turbofans behave more or less like this; the RM8A just happens to have a particularly pronounced thrust increase in afterburner because of its large bypass ratio.
Ah yes, sorry it slipped my mind that it was a turbofan. Thanks for the info :doh:
-
The thrust curve is a bit simplified in that diagram - it's not quite that linear with IAS, I'm pretty sure (compare to the thrust charts in the SFI).
Also, thrust numbers that are quoted in encyclopedias and the like are usually given for an engine static in a test rig on the ground. Mounting it in the aircraft reduces thrust because of losses in the intakes and to auxiliary equipment such as the generator, bleed air etc, but increasing airspeed increases thrust while on full AB because it gets more fresh air to burn. In other words, actual thrust in the air in different situations is quite different from the encyclopedia number. See my thread about the Viggen's afterburner for a lot more words about this.
Thanks, I'll be sure to read on your information in the other thread later.
However, conventional turbojet engines actually do not always create more net thrust with speed. The momentum change from air in to exhaust gases out decreases with velocity, but can increase again with proper design so the thrust vs. velocity is usually of a bathtub shape. But I guess that's what you mean by the thrust line being simplified. It only seems to show the increase.
F-14A of 70's Vs F-14A of 90's Vs F-14A Iranian
in DCS: F-14A & B
Posted
So I was doing some research and I found out that at least in the 1990's that the USN was either trimming their engines VERY low to the point that the TF30-P-414A was only producing a measley 17,077 lbf of thrust at MAX A/B or that the TF30-P-414A was actually that low on thrust. Other sources on the internet (including a study by the USN on engines for the F-14) state that the engine produces the same 20,900 lb of thrust as the earlier TF30s. Wish I could post it but it's from the 80's.
Therefore, I don't know if anyone would actually want a 1990's F-14A if the engine power is truly that low.
That said, does anyone know if that version of the TF30 was actually that underpowered or did the USN simply trim them down after the Cold War to keep them alive longer? I imagine the latter because that is lower than an F-4 Phantom's engines in thrust! :lol: