Jump to content

Benom8

Members
  • Posts

    20
  • Joined

  • Last visited

Posts posted by Benom8

  1. Yes, optional would be good (who knows what scripts people use that rely on pressing the keys a fixed number of times).

     

    Thanks I know about the f10 shortcut, but it's not really a workaround, as you need to find the target on the map and it also requires the use of the mouse, not just keyboard.

  2. Hi,

    When cycling views with the f-keys, it's very easy to skip past the object you were looking for and have to go through all the objects again to find it again.

    It's also, for example, not possible to quickly return to the f1 view briefly between time spent spectating on an object, without cycling through all objects in that category again to find it each time.

    Any or all of the following changes/additional bindings for the f-keys would be very handy for quickly switching to the view you want:

    1. F-keys remember to the last selected object in that category, and switch back to it when changing category
    2. An additional binding to cycle backwards through a category
    3. A 'previous view' keybinding to step back through the last few categories and objects recently viewed.

    Thanks,

    Benom8

     

    EDIT: I think the most glaring omission and least disruptive of the three to add is item 2. The others suggestions might need some more thought on the details, but something along those lines would be awesome.

    • Like 2
  3. 52 minutes ago, BIGNEWY said:

    for players there is no change, but the fix prevents a crash situation from happening. 

    thanks

    Being able to manually edit the .miz files to make certain modules optional to join a server is important to our group. Will this still check against only the requiredModules section in the miz file, or will editing that no-longer prevent users being blocked from joining?

  4. Hi,

    Just wanted to share my findings from updating liveries from the F1CE to the EE, in case it saves someone some troubleshooting. You need to set the right animation values in description.lua, otherwise you won't see the probe, updated cockpit version (for the external model), and some other small changes to the model. Based on one of the included liveries, I set the following animation params to non-zero values:

    custom_args = 
    {
    	[70] = 0.26,-- Mirage F1 cockpit
    	[987] = 0.1,--NOSE
    	[988] = 0.1,--RWR variant
    	[989] = 0.1,--OIL DRAIN variant
    }
    • Like 1
    • Thanks 1
  5. Hi,

    Being able to remove the mirrors completely is a neat feature, but I noticed that doing so gives the same FPS hit as having them rendering reflections. Brief track attached, sitting on the tarmac at Tinian, where mirrors seem to make a big FPS difference on my system. The only geometry behind the mirrors was the ground.

    With the mirrors on but not rendering reflections I got 60FPS (vsync limit), but with the reflections on, or mirrors removed it was down to around 40.

    Apologies if this is already known, I couldn't find a thread about it.

    Key system specs: i5-9600K, 32GB RAM, GTX 1660S.

    Mi24-Mirrors-FPS.trk

    • Like 4
  6. That's good news about the template!

    In the mean time, you can edit a copy of the dds file and include it in the same folder as your other livery textures. That way it doesn't affect any other liveries.

     

    Make sure you have the following line in your description.lua file (assumes the file you added to the livery is still called "mi-24p_evu.dds") :

    {"mi_24p_evu",	DIFFUSE, "mi-24p_evu", false};
  7. I noticed that in this map there's currently a flagpole on one of the perimeter fences slightly to the right of centerline when landing on runway 29 at Ercan. This is a real hazard when flying a 2.5 degree glideslope to the threshold. Wanted to query this as it seems an unlikely setup in reality.

    Screen_210824_195712.jpg

    • Like 1
  8. Hi,

     

    I think it would be handy to allow players to set the frequency presets for this and other airframes in some sensible way in-game. E.g. via an interactive kneeboard when landed at a friendly base. This would avoid relying on mission designers to set these presets/guess which ones would be useful - these can be hard to plan out e.g. if players want to use a particular frequency for their flight on SRS etc.

     

    Just a thought! 

     

    Best wishes

    • Like 5
  9. Just to add to the folklore on this, I was getting this issue sporadically (and only one black poly at a time) on my 1660S. Incidentally I was using an AMD 280X on this system previously. I haven't noticed these for the last week or so after I: Updated the drivers, cleared NVidia shader cache, cleared the DCS shader caches, repaired DCS, and cleared the DirectX shader cache. Fingers crossed they're gone. I underline the last step because I don't see it mentioned here yet, and maybe there was something lurking there from my old card.

    • Thanks 1
×
×
  • Create New...