-
Posts
25 -
Joined
-
Last visited
About NSAdonis85
- Birthday 03/23/1985
Personal Information
-
Flight Simulators
X-Plane 11/12, DCS World, IL2 1946/Cliffs Of Dover/ Battle of Stalingrad, Rise of Flight
-
Location
Serbia
-
Interests
Knowledge and understanding
Recent Profile Visitors
546 profile views
-
Mike Force Team started following NSAdonis85
-
I did loooong ago, never got any reply ever.
-
The issue still persists after yesterdays patch. dcs.log
-
user error JSOW acts like a JDAM when TOO Waypoint Designated
NSAdonis85 replied to NSAdonis85's topic in Bugs and Problems
Yea, I know about the DTC part and what prerequisites it entails to be included, the way the F-15E and F-14 handle waypoints with naming together with the mission tab is something that would make everyone's lives more easy with this in the long run on jets that have a more complex INS system that can handle more than 9 waypoints plus 9 correction waypoints (example in my mind here is the Carousel IVA unit). I don't know if it's accurate that the JSOW/TPod slaves to the altitude given IRL. Mentioning all this in documentation would be good too, so far neither of the 3 (A-10, 16, 18) has it as far as I saw. I do own the Apache too but I haven't gotten around to learning it enough to know how this works with it, the Ka-50 has it's own similar system already. Yea, Revan is my fav SW character (with both games, never got into SW:TOR enough) -
user error JSOW acts like a JDAM when TOO Waypoint Designated
NSAdonis85 replied to NSAdonis85's topic in Bugs and Problems
It seems so. Would be nice for the A-10, F/A-18 and F-16 to get the mission planning tab like the F-14/F-15E has tho, that would be a much better solution than this current one. -
user error JSOW acts like a JDAM when TOO Waypoint Designated
NSAdonis85 replied to NSAdonis85's topic in Bugs and Problems
I think I know why it is happening. Both when I tell the tpod to slave to a waypoint or I waypoint designate the JSOW it gives the altitude I set in ME (FL300), not the height above sea level as you can see on the screenshot, so if I even release the weapon it just goes dumb because of the alt diff. I don't have this issue with the F-15E because of the mission waypoints tab in ME. I'm including the miz file too just for reference. JSOW_Training.miz -
user error JSOW acts like a JDAM when TOO Waypoint Designated
NSAdonis85 replied to NSAdonis85's topic in Bugs and Problems
I will, thing is, I might have done something wrongly in the track, i wanted to just replicate the behavior, I'll rerecord it tomorrow. Is the setup errorless tho? -
NSAdonis85 started following Possible UB, G, GT and/or AS variants down the line
-
Topic name says it all.
-
Still happens in any Mirage F1 mission on Syria map. I have loaded into an F-14B, M F1CE, then Strike Eagle, made screenshots of it, including log file too. Note what happens when I hit Esc to bring up the UI in the 3rd screen. dcs.log
-
The tell-tale difference is in the frametime, I still have this issue BTW, altho i haven't checked it the last 3-ish patches, will report back when I check on it now.
-
wrong radar mode - not a bug A/G radar not working
NSAdonis85 replied to NSAdonis85's topic in Bugs and Problems
Oh, so this is among the new additions to the F-16C, haven't had time to read the mini-updates thread. -
When I hit A/G I get the radar as it was turned off in A/G mode, nothing helps to turn it back on. A/A mode works fine. Screenshot and log included. dcs.log
-
Don't you people read anything at all? It is an issue specific to the Syria map and the Mirage F1, all other planes are fine, including the F-15E and Apache. I at worst have 25fps with the rest save for the Enigma server which is unplayable for me since their 2.0 campaign (it'll have to wait on a new PC). I have 32Gb set for virtual memory.
-
I said I did: I run on mostly minimum to medium graphics settings. Your issues wouldn't be the same anyway. This is something specific to the Mirage F1 since it's the only module doing it, I have at the peak worst 25fps otherwise save for MP situations, pick any module out of the list in my signature they all perform the same way. Since I tried reinstalling the module completely and it didn't help. And Aerges seem to not care to even reply here which I find...interesting. Here's the log, and lets see what becomes of this. dcs.log