deadpool
-
Posts
604 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by deadpool
-
-
Planes just seem to swallow up the light instead of reflecting any of it, that is of non-player objects.
If I shine my taxi light on another player's plane it's illuminated by it, yet a floodlight on the map won't have the same effect.
I have no track file, but please find below a screenshot from a plane in a hangar ingame, as well as a reallife photo of a similar situation.
In general this also has the effect that in a moonlit sky where I can make out details on the ground in the light, I cannot say the same about my wingman flying 8m next to me. He is pitch black. There should be at least a little light reflected from him.
This is on open beta 2.5.6.61527.3 and I believe it came into the game with the lighting system overhaul a while back for nicer night-flying stuff.
-
Done, though this sadly means it's going to take ages to get fixed
-
I now had this in the F-16, too .. and it had something to do with the lights.
-
1
-
-
I had this today in the F-16. In sync with the strobe light, also had it when popping flares.
-
1
-
-
My wingman had it yesterday in the JF-17 as well. Different system, though WMR VR as well.
Though please have in mind that it's something inside DCS, as the black eye shows on the repeater screen as well and is rendered underneath the text layer of DCS.
This makes the JF-17 at the moment unplayable for me in VR!
-
Originally posted here:
-
Since there are two forums, and for better visibility and because I see this as a bug:
-
This is how it looks like with the ESC-Menu active:
-
1
-
-
All of a sudden I have one eye flicker black occasionally for me. This is also visible on the Flatscreen monitor's DCS window and when recording it I can see that the blackness is actually coming from underneath the textlayer .. so it seems to be something inside DCS doing this?
Attached two frames that I captured mere milliseconds apart (only modification is the censoring of the SRS IP and port):
The problem is amplified by a lot when turning on external lighting. When deactivated it's occuring about 95% less in above instance.
I have witnessed this problem so far only in the JF-17.
-
with normal INS
Plane ascends, baro altitude climbs, INS altitude climbs
Plane descends, baro altitude shrinks, INS altitude shrinks
with INS+GPS
Plane ascends, baro altitude climbs, INS altitude shrinks
Plane descends, baro altitude shrinks, INS altitude climbs
this only happens with a fast align .. you start, ins shows you at 170ft in incirlik .. ins+gps at ~30ft .. you fly around a short while .. land .. ins will show you at 170ft again .. ins+gps shows you at +8000ft or something ..
This is a video of it while ascending in flight:
https://www.youtube.com/watch?v=_TKiwsNeMQA
This is a video after landing when I switch GPS on off again, and it goes from:
INS +0170 toINS+GPS +00026 and then when I switch again to
INS +00266
https://www.youtube.com/watch?v=C30EtrIsmAk
-
https://youtu.be/x3NKK86K7Zc?t=74
I find it frightening that common sense doesn't prevail here. But I can understand better now why the F-16 drops chocks when switching from MRM to DGFT mode .. it makes no sense .. but I guess no one actually proved it to ED yet that it doesn't ..
Not the right approach when building a realistic airplane in my book.
Anyways .. to help current topic. above is a photo of an F-16 with chocks and an arresting hook which is added - most likely - because it would otherwise jump over the chocks and go.
Now I just have to say that I do not know if this is particularily the model and type of F-16 that ED builds in DCS, of course that would be a good reason to disregard this and wait for a photo of the specific model and type we fly in DCS with this hook. Yet I think we can assume that this chock-protecting-arresting-hook-setup is something universal on all modern F-16s .. unlike SDBs and other gimmicks that we won't be getting because they were .. ah .. never mind .. I digress.
-
In principle you are right about the AMRAAM, but also this transmission of datalink guidance (from STT) can be detected by an RWR.
That is why this Missile Launch Detection is available in the form of a warning.
But then you wouldn't know whom he is shooting it at.
It's broken. STT and SAM both are. There is no reason why SAM wouldn't give you a spike either, yet it doesn't ..
-
Probably Maverick in VIS mode.
-
https://forums.eagle.ru/showthread.php?t=257642
I posted that bug almost a year ago. But ed decided to call it intended behaviour.
Me and someone I know who flies the F-16 in real-life now just laugh about it. What can you do.
-
1
-
-
It happens because Mavericks jump back to VIS mode all the time ...
like when you go to MRM and then back to AG .. it will be in VIS mode again ..
or when you fired the last and switch modes back to NAV .. might end up in VIS mode .. and that shows you those bogus data.
-
Wake turbulence isn't anything important and is grossly exaggerated, that's why real world pilot curriculum makes a special point to emphasise how dangerous it is to pass behind another plane. Large aircraft like airliners (ie tankers) are potentially dangerous up to several miles AFTER they've passed by... So, yeah, I can see how sloppy formation flying can be a problem.
If the wings are wanting to roll while flying with someone/something, by definition it means you're in the wrong position.
If wake turbulence was programmed accurately and the plane was symmetrical I would tend to agree with you. Sadly we don't live in such an ideal world. But I read between the lines and don't think I need to discuss this further with you.
-
Out of curiosity. How hard is the strain on one's computer to have it turned on? My computer is very old, and I need all the FPSs I can get from it.
Sent from my ANE-LX1 using Tapatalk
I fly with an i7 4790k and a GTX 1070 and the only strain on my computer is the kicking it receives when these ridiculous wake turbulences flip the plane again.
-
Afaik an F-16 currently creates the same wake as an FA18 .. and yeah .. it's a paperplane when receiving it and we only joke about it anymore .. You can fly formation with someone and feel one of your wings wanting to go down either towards or away from him ..
Or you are affected by wake when flying on the outside of the turn of a turning tanker .. lol.
And the intensity is like being hit with a baseball bat on the side of your head at times.
I have great video footage of me landing in formation with someone and the wake turbulence from landing next to him combined with the ridiculous lateral friction (a problem that has been known since a year + a fix suggested and ignored) lead to a flipover in the most benny hill kind of fashion.
-
Does anyone know the RADAR technology employed in the F-14 and Viggen modules? I swear they did some form of ray-casting, and I swear this approach is different to aircraft like for instance the F-16C, F/A-18 and F-15.
I also swear the MiG-21bis' new RADAR system also does something along the lines of some form of limited ray-tracing/ray-casting if I'm not mistaken.
I'm pretty sure that the F-5E-3s RADAR is simplified, at least according to this.
I don't know about the RADARs of AI assets, such as our various ground units, ships and AI aircraft, presumably they're also pretty simplified.
There's also the issue of DCS terrains that model the Earth as if it was flat, which presents problems in and of itself. I'm pretty sure a workaround(?) is used for the RADARs but not sure what their limitations are. I guess some testing has to be done, but the flat Earth thing is really a discussion in and of itself.
EDIT: Quick test in the F-16C, my RWR picked up the RADAR of the Slava class CG while flying at 595 feet above the water at a distance of ~40.6nmi which seems about right according to this ( I should have LOS to the top of the ship at around 40nmi
The radar and the eyeballs of the AI are simplified to stupidity.
You fly a Viggen between hills at treetop level .. and you can see on tacview exactly when you are in line of sight of an enemy MiG21 .. because it will turn in on you.
Can't have been the radar .. so they must have perfect eyesight .. 30nm seeing a viggen at treetop level .. it's really boring.
-
It will come later.
It's not only the seat, you're also assisted by the overpressure mask helping you breathe ..
all not modelled, yet. and yeah, we all miss it.
-
Because at the moment what you have essentially gives you a box you can slew your TPOD on and got the emitter dead on.
And again .. this is if you even get the box visibly in the Hornet in the first place.
Afaik the HARM transmit an analog video signal for the HAS page that gets piped into your MFD much like the Maverick .. not really something that you can use to get azimuth etc. from easily.
-
Its not a simple as that. Nothing is slapped on without first being testing, and a official manual being revised to document new procedures for new integrated weapons so other pilots can be taught how to use it.
Using such line of reasoning to justify any weapon is a quite a slippery slope to getting totally speculative fiction genre of loadouts.
The difference between a hydra 70 and an APKWS is an added small section to the missile.
It is comparable to the F-5 dropping GBU-12 instead of a Mk-82.
Does the F-5 have any software to support the GBU-12? .. no .. heck no .. to it .. it's just the same drop system as with a Mk-82 .. the rest is done in the bomb .. There is no interface that you need, no connector, no special HUD symbology.
But .. maybe that's even too far .. the difference between Hydra 70 and APKWS are smaller. It could be compared to the impact fuze in your bomb being changed to a different type with the same aerodynamics, same interface to the plane, etc.
The one thing I could think of though is that the missile is slightly longer and potentially needs type approval for the airplane you want to stick it on for that reason alone.
Otherwise, I hope that ED just makes the missiles available for all Hydra-capable planes and helos by adding it as a new ammunition type for the launcher.
-
You don't need a supercomputer. Having an RCS lookup depend on angle, that's absolutely easy with a look up table (LUT).
The problem is that the entire radar engine seems to be not working on a reasonable approach but on wtfs ...
If a target turns cold on you in the f-16 .. it will disappear at hardcoded 20nm .. the whole missile guidance radar stuff is completely borked ..
then if you see defects like:
missile is desynced and goes active, and your RWR then gives you a launch warning of the plane that launched it, even though it's turned cold already .. you just know that under the hood it's implemented in a VERY VERY rudimentary way that's not even taking the physical or world model into account.
-
This happens to me on occasion. After FLCS BIT test finishes, I cycle the controls. Every now and then I will move the stick left/right and the ailerons, one or both, fail to move, and the stabs move much less than they should. Pitch and rudder cycle fine. After a few back-and-forth aileron cycles, they finally start working again.
Had that today and can totally back that up.
.png.d1d0f49a3b9fb817d2997c1e9752c481.png)
.png.e62dadb862128ca746883d1a8514f837.png)
Locked target still dropped switching to DGFT mode coming from MRM mode
in Bugs and Problems
Posted
I am very disappointed that it hasn't even been acknowledge .. but still is "as intended" even though there is reallife comments from a pilot + video evidence.
The frequency in which I posted bugs has decreased because I feel very demotivated.