Some suggestions for improvements for the next versions -4.5 ?
-
Thanks Viper-0,
I don’t use AL. I’m using TARGET since many years now in a hybrid mod (DirectX and TARGET Scripting for Master Modes A-A, NAV and A-G). I don’t have so many problem with TARGET.
I can use three layers programming mode and so much more!!!
Ex: When i’m using the Padlock in Master-Mode A-G, my padlock is looking Air-Ground targets on the ground. When my Master Mode is in A-A, my padlocking is lookking for aircrafts. In NAV Mode, My padlock look for Priority Threats, and so on. I can’t do that kind of layer programming with AL, by the way (or I don’t know how…).My suggestion was not for a HOTAS manager. My suggestion was relating to some little bugs in the Set-Up Controller using the SAVE or APPLY button. (Ex: Some valid callbacks are removed from the keyfile after a SAVE).
So SAVE or APPLY button in the main Set-Up interface of the Sim should be able to write it’s own valid keystrokes file, as it was before.
New F4 pilots who didn’t read this forum can’t figured out what is going on behind the scene… That’s my point. I know Alternate Launcher tool and I’m also able to edit tricky keystrokes files myself with a text editor. I’m only suggesting this upgrade for all newbee and for a better general user experience without the need of another external tool.
-
I think the raytracing that’s being talked about as nice and dandy isn’t raytracing per se, but global illumination + ray tracing. That is indeed a huge task and apart from Control and Metro no game has it implemented properly yet, only in parts, and none of these are even remotely on Falcon scale. Ray traced reflections are another matter. But anyway, I think you guys covered it all already, and I-Hawk is right here.
@Mav-jp i can create a separate topic for this if you like, may turn into a discussion. There I can attach weather maps, make a video etc. But before doing any of that, you should know that the weather maps I use are made in F4Wx 1.05, so perhaps the way cells are done has something to do with that? The effect of switching between Fair/Clear weathers has been there in my experience since forever, but I’m using the F4Wx all this time. So, are you still interested? It’s default theater of course.
-
@seifer said in Some suggestions for improvements for the next versions -4.5 ?:
by letting sim logic run alone, we get rid of several races and avoid having simloop waiting for campaign during simlogic
That sounds like the right direction to me! I think I’m able to see the benefits, in frame-time consistency.
@i-hawk the increased consistency in U3 maybe makes the 7ms stutter even easier to see, in the timing data… just run PresentMon or FrameView and plot this column. The spike/hiccup seems to be every 87th frame, like clockwork.
+7ms is enough to miss/drop a frame at 60hz (fixed) if cpu-time is over 10ms… with g-sync enabled, sadly, it’s more noticeable… I guess because a missed frame at 60hz is less jarring than an out-of-phase frame? or maybe my monitor is just quirky in g-sync mode.
Only other clues I can add:
- if I pause or freeze, in flight, it still happens every 87th frame (so maybe not weather or ground textures after all)
- if I speed up sim time (4x, 8x, 16x) the spike happens more frequently – but not 1:1 with clock speed… it seems to happen every 8 frames (at each of those clock speeds)… weird
-
@airtex2019 said in Some suggestions for improvements for the next versions -4.5 ?:
because a missed frame at 60hz is less jarring than an out-of-phase frame? or maybe my monitor is just quirky in g-sync mode.
I should add: I’m running 4k@60hz monitor now … which means my Displayport 1.2 cable is close to maxed out, so even though the following frame comes in ~7ms early it doesn’t help the pipeline “catch up” … that probably explains why g-sync ends up looking worse than v-sync, for my setup
So, my options currently seem to be (a) run 60hz fixed with v-sync, and accept occasional missed-frame (not really noticeable unless close to ground)
or (b) run 60hz g-sync, with an fps cap around 43… leaving enough free bandwidth to “catch up” without exceeding the 60hz speed limit imposed by my 4k monitor/cable
-
@seifer said in Some suggestions for improvements for the next versions -4.5 ?:
@molnibalage hi!
Raytracing is the future. But we are very, very far from this. In fact, we have never talked about this internally (at least not that I know).
But I can definitely see areas that can benefit from this. For example, our cockpit is too dark depending on the angle of the sun, even if the day is sunny and bright. This has already improved in U3, but it got to a point that if we make it brighter, the rest of the world becomes too bright as well.
Also, we have very limited lighting capabilities, as you can see from our airbase fake lights. Raytracing deals with this much more nicely, such that lights happen naturaly.
For now, we have more important stuff to fix
It is so resource eating thing that I happily live with “fake” lights.
Because the charm is BMS that you do not need a high end config for it. -
@depapier said in Some suggestions for improvements for the next versions -4.5 ?:
I think the raytracing that’s being talked about as nice and dandy isn’t raytracing per se, but global illumination + ray tracing. That is indeed a huge task and apart from Control and Metro no game has it implemented properly yet, only in parts, and none of these are even remotely on Falcon scale. Ray traced reflections are another matter. But anyway, I think you guys covered it all already, and I-Hawk is right here.
@Mav-jp i can create a separate topic for this if you like, may turn into a discussion. There I can attach weather maps, make a video etc. But before doing any of that, you should know that the weather maps I use are made in F4Wx 1.05, so perhaps the way cells are done has something to do with that? The effect of switching between Fair/Clear weathers has been there in my experience since forever, but I’m using the F4Wx all this time. So, are you still interested? It’s default theater of course.
Yea I am
Please provide a repro case
-
@molnibalage said in Some suggestions for improvements for the next versions -4.5 ?:
Because the charm is BMS that you do not need a high end config for it.
Yes but don’t build on that for the future, we are actually going to trespass… regardless of ray tracing or not.
-
Hello, my suggestion for the next version is maybe adding the ability to adjust the opacity of the MFD symbology. This way we can better make out the target behind the crosshairs.
-
@spotdott contrast / brightness … It is already there
-
@maxwaldorf doesn’t the contrast and brightness change the entire MFD? Sym would only adjust the text, crosshairs and other overlay information, not the raw radar/tgp video. The problem is sometimes the crosshairs are solid and there’s no transparency. A small object is partly obscured and hard to identify. If sym is implemented, the crosshairs can be faded with a bit of transparency and make the target behind it easier to see.
-
@spotdott said in Some suggestions for improvements for the next versions -4.5 ?:
Hello, my suggestion for the next version is maybe adding the ability to adjust the opacity of the MFD symbology. This way we can better make out the target behind the crosshairs.
If such a function exists in real MFD …
EDIT: oh is it? I did not know SYM button works like that -
@chihirobelmo I didn’t know about this either until I saw the DCS video of the Viper GM radar mode
-
@MaxWaldorf is there a option or plan in the next version to implement a working Turn and Rate Coordinator?
-
@spotdott said in Some suggestions for improvements for the next versions -4.5 ?:
@chihirobelmo I didn’t know about this either until I saw the DCS video of the Viper GM radar mode
I would never take DCS as solid material reference
As usual many things are wrongly implemented in this video so let’s be careful
-
@mav-jp My little finger told me that real viper pilots would kill to have such resolution on their AG radar display
-
@i-hawk said in Some suggestions for improvements for the next versions -4.5 ?:
@molnibalage said in Some suggestions for improvements for the next versions -4.5 ?:
Because the charm is BMS that you do not need a high end config for it.
Yes but don’t build on that for the future, we are actually going to trespass… regardless of ray tracing or not.
Am I understanding right?
Does this mean that the BMS will demand in the future a strong VGA and CPU?I just updated my rig to a 1660S but even this was quite expensive because of the lack of chips and ******* crypto miners…
It was 50% more expensive than it was years ago. Just after I bought it was raised with 45%. So today a 1660S is about 2.5 times (!!) more expensive than was 3 years ago. A totally outdated VGA which is 2 generation older than the latest.
-
@molnibalage said in Some suggestions for improvements for the next versions -4.5 ?:
@i-hawk said in Some suggestions for improvements for the next versions -4.5 ?:
@molnibalage said in Some suggestions for improvements for the next versions -4.5 ?:
Because the charm is BMS that you do not need a high end config for it.
Yes but don’t build on that for the future, we are actually going to trespass… regardless of ray tracing or not.
Am I understanding right?
Does this mean that the BMS will demand in the future a strong VGA and CPU?I just updated my rig to a 1660S but even this was quite expensive because of the lack of chips and ******* crypto miners…
It was 50% more expensive than it was years ago. Just after I bought it was raised with 45%. So today a 1660S is about 2.5 times (!!) more expensive than was 3 years ago. A totally outdated VGA which is 2 generation older than the latest.
What do you suggest then? that we should stay forever with 1KM res terrain, no VR and “flat” 3D models? Come on man! Chips prices are crazy indeed but we can’t forever support low-end HW.
And BTW, even my 4 year old laptop with 6700HQ and GTX-1050 mobile can run “heavy future version” on FHD with MSx2 and ~50 FPS in TE. So medium cards will still work assuming you stay on FHD and no VR.
-
As Mav-jp mention the blank spot occured in DBS1 and DBS2 A-G radar functions
it was implemented wrong right now in DCS
-
@i-hawk said in Some suggestions for improvements for the next versions -4.5 ?:
@molnibalage said in Some suggestions for improvements for the next versions -4.5 ?:
@i-hawk said in Some suggestions for improvements for the next versions -4.5 ?:
@molnibalage said in Some suggestions for improvements for the next versions -4.5 ?:
Because the charm is BMS that you do not need a high end config for it.
Yes but don’t build on that for the future, we are actually going to trespass… regardless of ray tracing or not.
Am I understanding right?
Does this mean that the BMS will demand in the future a strong VGA and CPU?I just updated my rig to a 1660S but even this was quite expensive because of the lack of chips and ******* crypto miners…
It was 50% more expensive than it was years ago. Just after I bought it was raised with 45%. So today a 1660S is about 2.5 times (!!) more expensive than was 3 years ago. A totally outdated VGA which is 2 generation older than the latest.
What do you suggest then? that we should stay forever with 1KM res terrain, no VR and “flat” 3D models? Come on man! Chips prices are crazy indeed but we can’t forever support low-end HW.
And BTW, even my 4 year old laptop with 6700HQ and GTX-1050 mobile can run “heavy future version” on FHD with MSx2 and ~50 FPS in TE. So medium cards will still work assuming you stay on FHD and no VR.
Nope, I’m on side of upgrading but I’m not on side which will lead that you can’t play in FHD without 2060 or higher card and 32GB+ memory.
If you check the Steam stats 66% of players are playing in FHD and the most widely used VGAs even today is the 960 and 1060 series.
-
@molnibalage a 1080 works fine so fardon’t worry…