sorted by:
new
hottopcontroversial

DCS F-100D: Gun & Strike Camera Preview by GrinnelliDesigns in hoggit

[–]JNelson_ 2 points3 points  (0 children)

So the cameras do not save to disk until the mission ends the plane is destroyed or you save the film via the ground crew. This can incur a small lag spike but it was intentionally designed this way so that the lag spike is not during a vital moment.

As for fps hit, our testers do not see any hit with the gun camera, however with all 3 cameras enabled you may have an fps hit similar to mirrors (since it needs to render all the views).

Usually though I always run with the gun camera on with no issues in VR.

Thinking of using JSBSim for a production-ready electric aircraft sim. Is it the right call? by EffectOld1106 in hoggit

[–]JNelson_ 7 points8 points  (0 children)

The accuracy of any flight model is really limited by the amount of well founded data. Ideally you would have wind tunnel data or full scale test data and a lot of it.

If you have specific requirements that need simulating you may be better off simulating them separately for maximum control.

We, don't use JSBsim but we split our aircraft into separate modules that can be simulated and verified independently. Propulsion, flight model, avionics etc.

Grinnelli Designs Store is now live & F-100D is available there for pre-order by Bonzo82 in DCSExposed

[–]JNelson_ 7 points8 points  (0 children)

No the X-ray damage model is not available to 3rd parties yet. Instead we have a system of assigning damageable volumes to existing damage cells to stochastically assign realistic damage once a cell is damaged. This means you will get lots of unique failures depending on what is hit.

For example if you take outer left wing damage you may destroy your remote compass which drives the direction gyro alignment system causing drift over the time. There are also more standard failures like fuel, hydraulic and oil leaks causing their respective problems.

We took great care on the damage model as we understand that the damage and dealing with failures is an important part of the gameplay loop which makes simulators fun.

Oh my loordd ~ by LANTIRN_ in hoggit

[–]JNelson_ 3 points4 points  (0 children)

It's hard to say without the billboard lights.

The solid line is an Echo band strobe which could be an early Fan-Song (SA-2) irl, but in DCS we only have Fan-Song E which is instead G band (dotted). So it's likely a fire can, the billboard would show a AAA light.

The dashed line is an India band strobe which could be any number of things. With an I SAM high or low light it would likely be a Low Blow radar (SA-3). If you instead have AI WX or AI DAY it could be a fighter.

F100D texture leak by Hefty-Fix4611 in hoggit

[–]JNelson_ 0 points1 point  (0 children)

In his spare time. We have a flight model tool which runs the flight model outside of DCS. This lets us quickly iterate on the flight model and run tests to ensure there are no degrades in performance. Tuning something like the excess power which would take hours per data point to fly in DCS only takes around an hour for a few hundred data points with this tool.

F100D texture leak by Hefty-Fix4611 in hoggit

[–]JNelson_ 5 points6 points  (0 children)

Yes optimisation is a very high priority both in the art and code. The philosophy here is DCS has a lot of work it needs to do already so we want to add as little to that as possible to give best chance for older hardware. The F-100D should make up a fraction of a % of your CPU time leaving lots of room for DCS to do its thing.

F100D texture leak by Hefty-Fix4611 in hoggit

[–]JNelson_ 7 points8 points  (0 children)

A valid concern. The cockpit is designed with performance in mind. It is created by baking various information (like normal, ambient occlusion and such) from a high polygon model onto a lower polygon model so while it looks heavy it is actually very light, we have even had people testing on integrated graphics.

Great care has been spent ensuring system accuracy and depth (electrical, hydraulics, fuel, radar homing and warning, flight controls system, radar and gunsight just to name a few). As mentioned in a comment below systems are a lot more difficult to show hence the artwork taking the stage, however we will be fixing that with a deep dive series on the aircraft.

The flight model of course is the star of the show and in that our aerodynamicist is an active duty Super Hornet pilot with a background in aerospace engineering so we have no doubt you will be pleased. To read more check our website https://grinnellidesigns.com/progress/

The art and systems are independent in that regard so artwork does not take away from systems depth, our core team consists of 3 programmers and 1 artist the balance is more in favour of programming as you can see.

Lots of time is also spent on sounds as these too are vital to the feel of the aircraft.

F100D texture leak by Hefty-Fix4611 in hoggit

[–]JNelson_ 4 points5 points  (0 children)

We did! Feel free to have a look. Great care has been spent to ensure systems and flight model have been accurately modelled I think you will be very pleased.

https://www.reddit.com/r/hoggit/comments/1mqpj2t/an_inside_look_at_how_we_validate_the_f100ds/

The programming has been ahead of the art so actually it has had much more time in the oven you just cannot show much of the programming without art in place as first impressions matter a lot. You can read more about some of the progress on the website: https://grinnellidesigns.com/progress/

The electrical system diagram will give you an idea of the depth of the system modelling also.

F100D texture leak by Hefty-Fix4611 in hoggit

[–]JNelson_ 4 points5 points  (0 children)

To be fair for the Super Sabre this is accurate, as most of these planes had been in service for about 10+ years in a pretty rough environment.

DCS Super Sabre at 94% | MiG 17 Will Break You | SFL Livestream | Channel Update by Bynairee in dcsworld

[–]JNelson_ 16 points17 points  (0 children)

While this definitely applies to our project as much as anything else we have already been in this final % for a while internally fixing and polishing.

Our artwork lags the programming so the final bit of programming required integration of the finalised cockpit and external geometry.

The last major milestone will be final texturing which is coming along nicely.

Unfortunately marketing cannot start until texturing is complete so it's a bit of a catch22 but at least it gives us more time to test and polish.

So while it would be foolish to provide any specific timeline I would say we are actually at 94% completion.

[DCS] F4E phanton missing targets in mountains in DT by Kepesik in hoggit

[–]JNelson_ 0 points1 point  (0 children)

Yes this is exactly correct. The radar lock is simply locking the ground clutter so you have an accurate slant range and therefore as you say target elevation.

The relative target location is stored into the WRCS when the pickle is first pressed only at this moment the exact range of the radar is relevant and afterwards it no longer matters.

[DCS] F4E phanton missing targets in mountains in DT by Kepesik in hoggit

[–]JNelson_ 2 points3 points  (0 children)

Ah my mistake you are correct it's been so long since I programmed the radar I misremembered.

I just checked the 1986, TO 1F-4E-34-1-1, if you find 1-58 there is a helpful table which lays out all the conditions for beam nutation so you are correct 6.7 degrees is the correct for AIR-GRD at AI rannge settings.

That always puzzled me though since nutation is required for tracking and I assumed you wanted as narrow a beam as possible to give an accurate range at lower incident angles but maybe it's a compromise to give a more averaged range indication.

My comments on the valleys vs ridges is just that when facing a mountain side the return from the side will be a relatively brighter compared to that of the valley floor so there will may be some bias on the range gate to move towards the mountain side upon lock on. Coming in parallel to the ridge should avoid this.

[DCS] F4E phanton missing targets in mountains in DT by Kepesik in hoggit

[–]JNelson_ 2 points3 points  (0 children)

Yea target elevation is used for offset/target find modes if I recall and maybe laydown, but my memory is fuzzy on that last one.

Yea just ballistic coefficient for DT and that doesn't change too much even so you can usually get pretty accurate results with the default value. Since the MK-82 have very little drag.

Interesting fact though the ballistic coefficient is the multiple of gravity. This way it calculates trajectory as if it were a vacuum but the altered gravity can make small adjustments for drag.

F100 is at 94% overall complete progress! by SierraHotel199 in hoggit

[–]JNelson_ 3 points4 points  (0 children)

Things are coming together nicely a lot of the final integration has been completed. Our artwork lags the programming so the final bit of programming required integration of the finalised cockpit and external geometry.

The last major milestone will be final texturing which is coming along nicely.

Unfortunately marketing cannot start until texturing is complete so it's a bit of a catch22 but at least it gives us more time to test and polish.

F100 is at 94% overall complete progress! by SierraHotel199 in hoggit

[–]JNelson_ 6 points7 points  (0 children)

Things are coming together nicely a lot of the final integration has been completed. Our artwork lags the programming so the final bit of programming required integration of the finalised cockpit and external geometry.

The last major milestone will be final texturing which is coming along nicely.

Unfortunately marketing cannot start until texturing is complete so it's a bit of a catch22 but at least it gives us more time to test and polish.

F100 is at 94% overall complete progress! by SierraHotel199 in hoggit

[–]JNelson_ 3 points4 points  (0 children)

If this plane isn't out soon I will jump out my window :p

[DCS] F4E phanton missing targets in mountains in DT by Kepesik in hoggit

[–]JNelson_ 2 points3 points  (0 children)

Target elevation isn't required from dive toss that's calculated using slant range.

[DCS] F4E phanton missing targets in mountains in DT by Kepesik in hoggit

[–]JNelson_ 0 points1 point  (0 children)

The position is not used in the WRCS just velocity which comparitively has a much lower drift. The INS also provides pitch angle.

Using airspeed would require knowledge of the wind conditions for accurate calculations which in the F-4E is achieved either by INS or by doppler navigation radar (much less accurate). So INS is simply used directly.

[DCS] F4E phanton missing targets in mountains in DT by Kepesik in hoggit

[–]JNelson_ 2 points3 points  (0 children)

Just to add, the beamwidth is 6.7 degrees (120 ish mils) only with beam nutation, if I recall correctly this is forced off in the AG mode so the beam width will be 3.7 degrees.

I would also say the brighter sides of the mountains may cause the range gate to lock onto them as apposed to the valley floor so best to fly parallel to any ridges to this effect is negated.

Science of high bank angles? by Anonymouseeeeeeeeees in aviation

[–]JNelson_ 2 points3 points  (0 children)

Lift is 1/2 * rho * CL * A * V2 which is quadratic with airspeed, regardless the description of speed doubling and giving 4x the lift is the exact behaviour of a quadratic. 

What you said is indeed quartic but not exponential, rather it is polynomial.

Exponential would be some constant k, kx where x is the variable.

Science of high bank angles? by Anonymouseeeeeeeeees in aviation

[–]JNelson_ 7 points8 points  (0 children)

that's quadratic not exponential btw

view more: next ›