dr. hladik
-
Content Count
238 -
Joined
-
Last visited
-
Medals
Everything posted by dr. hladik
-
Jets - Sensor overhaul (Radars, IRs, Lazors, PGMs)
dr. hladik replied to oukej's topic in ARMA 3 - DEVELOPMENT BRANCH
Radar range change and target filtering - it is easy to implement, however it is hard to find keys to control it. Any ideas?- 957 replies
-
- 4
-
-
- electronic warfare
- radar
- (and 8 more)
-
Jets - Custom Panels (GPS, Camera feeds, ...)
dr. hladik replied to oukej's topic in ARMA 3 - DEVELOPMENT BRANCH
> Is there a specific reason why we have keybindings to close the display? No specific reason. It just could be handy if you have controller with 20 buttons.... -
Jets - Sensor overhaul (Radars, IRs, Lazors, PGMs)
dr. hladik replied to oukej's topic in ARMA 3 - DEVELOPMENT BRANCH
> Any word on missile guidance depending on the aircraft active/passive systems and the weapon's sensors? Ammo will use the same system.- 957 replies
-
- 5
-
-
- electronic warfare
- radar
- (and 8 more)
-
Also vehicle aim cursors are no longer visible on veteran difficulty
-
CCIP is now available only in MFD or optics
-
CCIP not being part of HMD - acknowledged
-
Advanced Helicopter FDM Feedback
dr. hladik replied to aluc4rd's topic in ARMA 3 - DEVELOPMENT BRANCH
1) Yes, damage is handled by our engine and according to hitpoints damage we are changing parameters of RTD simulation. While RTD does provide some damage system, it was rather unstable and hard to control. And as we need to be able to switch between our and RTD simulation at any time, we cannot fully utilize all features RTD provides. 2b) Our solution is probably not good enough :). Will check it (no promises). 3,4,5,6) limited manpower... -
Advanced Helicopter FDM Feedback
dr. hladik replied to aluc4rd's topic in ARMA 3 - DEVELOPMENT BRANCH
1) It is based on stabilizer position. HitHStabilizerL1 will affect stabilizers on the left side of helicopter 2) Engine type="ConstantRPMEngine">. ConstantRPMEngineis a class name from RTD 3) We are supporting only RTD::ConstantRPMEngine 4) Weird, there were no changes in RTD for APEX. 5,6) No. Those existed only for TKOH. It would be very inconsistent with other vehicles to have this still enabled. And we do not plan to re-enable them. Sorry. -
rev 137959 pilot camera improvements - improved controls when camera is lcoked - supported laser designator - pilotCameraRotX and pilotCameraRotY anim sources - new script commands: getPilotCameraPosition, getPilotCameraDirection, getPilotCameraRotation, getPilotCameraTarget, hasPilotCamera, setPilotCameraDirection, setPilotCameraRotation, setPilotCameraTarget
- 478 replies
-
- 10
-
-
good news: prototype of laserDesignator is ready more good news: controls are improved bad news: you have to wait after my vacation :P
- 478 replies
-
- 12
-
-
Exactly. p3d files for 95% of all the roads do not exist as they are generated by engine. How to add p3d road - I believe airports are still based on p3d files
-
Fixed Wing Flight Model (dev branch)
dr. hladik replied to dezkit's topic in ARMA 3 - DEVELOPMENT BRANCH
Not true.- 874 replies
-
- 1
-
-
- flight model
- flying
- (and 3 more)
-
Maybe in second iteration of improvements after Apex is released.
-
There is still some work planned. But after Apex.
-
see https://forums.bistudio.com/topic/189734-targeting-improvements/?p=3014700
-
Is planned for this era.
-
One step at a time.
-
Well, the result might be almost identical and laser designation is much nicer solution, however manually guided missiles are much easier to implement...
-
ok, so to summarize current state Camera controls - improvements are in progress CCIP - should be out soon CCRP - not planned Laser designator - considered for second iteration* Manually controlled missiles for pilots - good idea, might happen in reasonable time frame Autopilot - not being considered Radar improvements - considered for second iteration* Locked target name indicator - some changes are being considered, but mostly need to wait for second iteration Functionality unification with normal turret - should happen in reasonable time frame *second iteration will not happen before APEX is released edit: FCS, tanks - acknowledged, would be nice...
-
Valid, but off-topic :)
-
Yes, there are some changes, new features and new bugs. Please read https://forums.bistudio.com/topic/189734-targeting-improvements/. allowTabLock - will not disable locking, only Find_next_target functionality (should still work) canLock - now it just describes if weapon can be locked (guided missile), however if vehicle has some scanner (ir, nv, laser), then vehicle is able to mark that target. So, if you want to disable any marking, you need to remove scanners. And if you need to remove marking only for some turret positions - you need to wait a day, or two, as we have not yet introduced possibility of this combination... :unsure:
-
rev 135665 - "Lock UAV Turret" action (default LCtrl + T) now locks camera on position / target (if target is markable) - Num1-9 now also controls camera (num5 will return it to default direction)
-
Will be discussed.
-
Is being considered.
-
We cannot really use PIP for anything important, as it is very performance demanding and can be disabled in options.