Jump to content

Recommended Posts

Posted
YES. Its as though the plane spawns partially buried and explodes as soon as you hit FLY

 

If you're on the Stable release then that's an ED problem. It has been fixed on the Open Beta branch but hasn't shown up on stable yet.

Posted

sorry got no track yet - i am gonna investigate the exact circumstances as soon as i get onto a dcs machine

 

i'll post them as soon as possible

sigpic.png.4d2403c54e341ae5cf45e3309e87cb2c.png

Posted
I am looking forward to when my A-4 Simpit is complete and I can play on it with this.

 

 

How far are you into it? I started to work on my front panel, going along nicely

 

Marc..

Posted
I noticed that in the USAF Aggressor "country" A4 has only the unmarked skin.

It would be great to have also some aggressor skins.

 

noticed that too .. all skins should be available ..at least the agressor ones

Intel I7 - 10700 K @ 3,80GHz / 64 GB DDR3 / RTX 3090 / Win 10 Home 64 bit / Logitech X56 HOTAS / HP Reverb G2  

Running DCS on latest OB version 

 

Posted

Minor request, if you guys got a minute.

 

in the current controls settings, it only allows the keyboard to have bindings for "Engines start", and "Engines stop". For all other controllers the option to bind those is greyed out.

 

could you unlock the Engines start/stop settings so that those can be bound to any controller button?

 

Thanks!

Posted (edited)
Minor request, if you guys got a minute.

 

 

 

in the current controls settings, it only allows the keyboard to have bindings for "Engines start", and "Engines stop". For all other controllers the option to bind those is greyed out.

 

 

 

could you unlock the Engines start/stop settings so that those can be bound to any controller button?

 

 

 

Thanks!

 

 

 

Added to the todo list. Should be a simple fix.

 

Edit: Fixed for the next patch

Edited by heclak
Posted
This is the manual, or a "reduced" version of the manual ?

There is no official manual for the A-4E-C. But being one of the coders for the module, that is as close/accurate as it gets. However, it is still a work-in-progress and I am writing it as I learn each system of the aircraft. You can use the actual NATOPS manual if you prefer an extremely detailed manual too. I am writing it based on the NATOPS manual.

Posted
There is no official manual for the A-4E-C. But being one of the coders for the module, that is as close/accurate as it gets.

 

Cool, it's not a problem, I just wanted to know if there was a detailed oficial manual.

It's even better like that, I'll not feel guilty for flying it without reading the manual first ;)

Posted
Added some highly requested key bindings for the next patch.

Brilliant :thumbup: I always wondered, is it very difficult to add the CW/CCW bindings?

Because some devs of payware modules seem to really struggle with it (or just don't care).

A warrior's mission is to foster the success of others.

i9-12900K | RTX 4090 | 128 GB Ram 3200 MHz DDR-4 | Quest 3

RAT - On the Range - Rescue Helo - Recovery Tanker - Warehouse - Airboss

Posted
Brilliant :thumbup: I always wondered, is it very difficult to add the CW/CCW bindings?

Because some devs of payware modules seem to really struggle with it (or just don't care).

It depends on how the system was coded. It took a bit of time to figure out how I should do it but it was really straightforward after that. I made sure I figured it out as I know some people really need it. I would describe difficulty as 1.5 out of 5?

Posted
@ Heclak: Many thanks for adding the RWR/ECM pages to your guide! Now I know how to use them. :smilewink: :thumbup:

 

 

 

No problem. However, the visual ECM panel is based off the APR-25 which isn’t done. The function is currently based on the older APR-23 so the only thing you need is the APR-23 power switch and the volume knobs.

 

That’s why the orange boxes. I’ll look into explaining those better. Still a work-in-progress.

Posted (edited)
Jacks you need to log in to the Scooter, let it fully spawn, then back out to Spectator or another aircraft, and once that spawns in you can go back to the Scooter and the click spots will be in the right locations.

Is this a joke ?

 

I have the Clickarea problem, have to click outside the controls ... if it's not a Joke, can someone explain me how to do that ? Is it only for MP ? What's the Scooter ?

 

 

Added some highly requested key bindings for the next patch. Please feel free to suggest key bindings that are missing or not working.

I think the HUD ilumination keys are not working, Gun Sight roulette doesn't react

Edited by cercata
Posted
Is this a joke ?

 

I have the Clickarea problem, have to click outside the controls ... if it's not a Joke, can someone explain me how to do that ? Is it only for MP ? What's the Scooter ?

 

Select the scooter in roles, click fly, then Escape, Select Role, Back to Spectator, then back to the plane. The Scooter is one of the A-4's many nicknames.

Posted (edited)
Select the scooter in roles, click fly, then Escape, Select Role, Back to Spectator, then back to the plane. The Scooter is one of the A-4's many nicknames.

Thanks :)

 

"Select role" is only available in Multiplayer, isn't it ? Can you recommend me a server to practice with the "Scooter" ? I was in SP till now.

 

BTW, the scooter is trully amazing, yesterday was my first day with it, still have to map somethings, and learn others, but I'm liking it as much as the F-5E

Edited by cercata
Posted

I think the HUD ilumination keys are not working, Gun Sight roulette doesn't react

 

I'll look into this, looks like its a generic keybind leftover from the FC3 commands and it shouldn't have been there at all. I might consider removing it altogether as the A-4E HUD brightness will increase to a point where it will turn off.

 

Is this keybind even useful/needed? I hardly ever change the HUD brightness.

Posted
Is this keybind even useful/needed? I hardly ever change the HUD brightness.

 

For navigation, I would like to switch it off, and that's one of the most difficult to click controls in VR, with the clic-area drift problems

Posted
I'll look into this, looks like its a generic keybind leftover from the FC3 commands and it shouldn't have been there at all. I might consider removing it altogether as the A-4E HUD brightness will increase to a point where it will turn off.

 

Is this keybind even useful/needed? I hardly ever change the HUD brightness.

 

I'm changing the gunsight brightness quite often. If it's too bright, you can't really see your target, especially at night. I never use keys for adjusting the brightness, but the rotary knob. I'm no friend of keys. Most things I can't assign to my HOTAS are activated or changed with mouse clicks or the mouse wheel.

 

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...