Is RAZBAM or ED reading this section or the Bugs section?

[eddyimac]

Several important BUGS have been reported since the last OB. Neither RAZBAM nor ED gives any response. We all invest money so that the modules and DCS in general go better every day, not worse. The Harrier was a fantastic module that worked reasonably well. Please take note of the reports !!

Edited June 9, 2020 by eddyimac
orthography

[Fri13]

I would ask at least that the reports and brought strange behaviors via discussions would be marked with the change of the thread title by the moderator as ED does, like those [CORRECT AS IS], [iNVESTIGATING] etc.

 

At least we would know that developers has received the information and there is work to be done for it (or correct as is).

[ruxtmp]

Please be aware that the AV-8 and the Mirage are modules that RAZBAM are using to learn how to develop code for DCS. Likely they have not yet been able to figure out how to code the corrections or determine what is causing the bug.

[eddyimac]

Please be aware that the AV-8 and the Mirage are modules that RAZBAM are using to learn how to develop code for DCS. Likely they have not yet been able to figure out how to code the corrections or determine what is causing the bug.

 

 

Learning with payment modules? is it a new selling concept? So we have to pay for them to "learn"?

[Fri13]

Learning with payment modules? is it a new selling concept? So we have to pay for them to "learn"?

 

Every worker in this world will learn a lot of things while working. There is no school or education that will teach you everything (or even most of the things) for the profession.

 

So yes, every developer is constantly learning new things to do things differently (and better).

And when your programming is tightly linked to another company products (their SDK, their core simulator etc) that gets changed between patches not at all or a lot, then you are learning a lot of things how to get things working with their code.

 

The ED SDK might include some kind concept/sample codes for given things, so that new studios can look at it and get an idea how things works. But if you are doing own new things, like ARBS, A-G radar or missile IR-seeker to guide radar etc that ain't in the SDK, then you are on your own.

 

So like in this case, while Heatblur had coders to go a head and develop a own A-G radar for Viggen, Razbam was smart to leave that whole thing out and wait that ED is developing their A-G radar before they will consider to make a AV-8B+ that is same as N/A but just with the radar scope instead ARBS (they share the same exact flight manual in reality, there are just pages that simply explains when something is different between the N/A and + variants).

 

So if ED would be nice, they could literally offer a code for the APG-65 Radar from F/A-18C hornet from the parts that modes it has. Or at least let Razbam take a look at it and fasten the process, as in reality those are same radars (except Harrier has smaller radar antenna) so it could just make even ED job easier.

 

Do the Razbam learn from such thing? Not so much as if they would write it all from themselves, but then again as it is symbiosis that ED gets money when studios sell something etc and when it is easier to maintain some features, it is win-win situations.

[ruxtmp]

Learning with payment modules? is it a new selling concept? So we have to pay for them to "learn"?

 

I think so, or at least that what appears to be suggested. RAZBAM had been a MS FSX developer and decided to get into the DCS business once that game/sim ended. I can agree that 3rd party developers have a learning curve and all first modules are a bit of "on the job learning". It just appears that this developer was not fully transparent at how they intended to support these two modules when they were released in Early Access. I pretty much just use the harriers and mirages as AI backfill in my missions. I mean I spent money on the WW2 asset pack so I figure I got 2 planes and LHD asset pack.

[eddyimac]

Every worker in this world will learn a lot of things while working. There is no school or education that will teach you everything (or even most of the things) for the profession.

 

So yes, every developer is constantly learning new things to do things differently (and better).

And when your programming is tightly linked to another company products (their SDK, their core simulator etc) that gets changed between patches not at all or a lot, then you are learning a lot of things how to get things working with their code.

 

The ED SDK might include some kind concept/sample codes for given things, so that new studios can look at it and get an idea how things works. But if you are doing own new things, like ARBS, A-G radar or missile IR-seeker to guide radar etc that ain't in the SDK, then you are on your own.

 

So like in this case, while Heatblur had coders to go a head and develop a own A-G radar for Viggen, Razbam was smart to leave that whole thing out and wait that ED is developing their A-G radar before they will consider to make a AV-8B+ that is same as N/A but just with the radar scope instead ARBS (they share the same exact flight manual in reality, there are just pages that simply explains when something is different between the N/A and + variants).

 

So if ED would be nice, they could literally offer a code for the APG-65 Radar from F/A-18C hornet from the parts that modes it has. Or at least let Razbam take a look at it and fasten the process, as in reality those are same radars (except Harrier has smaller radar antenna) so it could just make even ED job easier.

 

Do the Razbam learn from such thing? Not so much as if they would write it all from themselves, but then again as it is symbiosis that ED gets money when studios sell something etc and when it is easier to maintain some features, it is win-win situations.

 

 

I understand your argument, but I don't share it. With this strategy you improve a module and ruin 3. It is like putting the cart ahead of the horses. It would be a lack of coordination. I have been a developer, professor and researcher for 30 years; And I honestly think that this methodology is incorrect. However I am hopeful that they can solve the problems in the best possible way.

[Fri13]

I understand your argument, but I don't share it. With this strategy you improve a module and ruin 3.

 

Well that was hard fact, you don't know everything because you are professor or researcher.

And whole life is about learning new stuff, it is called silent information and known as well "education comes with profession".

 

And what comes to that style, software development is not science, it is art and science. That is what separates hackers from other programmers, that they can see things clever way and make things better or fun.

sure a software business is serious business, and it shouldn't be so that you take others money to give a crap, but that is life. That happens everywhere. Stock markets are nothing more than psychological gambling that is covered in lies of economic science. And whole countries are ruined and wars started when someone wants more money.

 

So someone coming to business in DSC world and truly tries their best is welcomed, even if they learn in progress and needs assistant. As long a case T.1A Hawk doesn't repeat, things are fine so long developers are ready to learn, improve and work.

 

Companies developing for DCS are small, and much larger companies waste billions of dollars for software projects that are as simple as getting a print out of a person papers....

Or takes years to fix a small problems as one line coding error.

 

It is like putting the cart ahead of the horses. It would be a lack of coordination. I have been a developer, professor and researcher for 30 years; And I honestly think that this methodology is incorrect. However I am hopeful that they can solve the problems in the best possible way.

 

Please explain.... Why shouldn't ED provide SDK and sample codes? Why ED should demand everyone develop their own codes for everything? Why shouldn't studios allowed to share code between for common code base from parts they could?

 

Razbam does have a challenges and lots of unfinished features, but most annoying is that they do not communicate, almost at all.

Customer service is very important job, and it is critical element for good relationships and business. Yet that task is very overlooked by developers, as well business people.

 

And as this year ED changed their way to deal with threads topics to inform official statement, it makes a lot of difference for better.

[Fri13]

It just appears that this developer was not fully transparent at how they intended to support these two modules when they were released in Early Access.

 

While Razbam actions speak behalf, it is for me more like that they were caught with the demand for quality. As somewhere did I read that razham said that they make a lot just by guessing, before they learn better. Why example Mirage got major changes to it as Ada approached and told what is wrong. And harrier got major changes as it was forum members who picked up details from NATOPS and videos and explained them to razbam.

 

So in my eyes it is more that razbam is learning that on what level to produce features, than coding itself. As you can be excellent programmer, but if you implement systems wrong or don't even know how they work, how could you do it right?

 

I pretty much just use the harriers and mirages as AI backfill in my missions. I mean I spent money on the WW2 asset pack so I figure I got 2 planes and LHD asset pack.

 

I have had mirage parked for long time, as well Harrier. As I am waiting festures fo be added that were told to lack years ago.

but it doesn't mean that they don't get them fixed, if they want to.

 

Problem just is that if you promise that they don't release any other modules before finishing already existing, and then you start showing progresss new ones, it is just bad PR. Even when everyone should know that if 3D modelers and texture artists needs to work as well while programmers finish other existing modules, but it is just the marketing side that makes bad taste.

[eddyimac]

Well that was hard fact, you don't know everything because you are professor or researcher.

And whole life is about learning new stuff, it is called silent information and known as well "education comes with profession".

 

Of course I don't know everything! But I do know that art and science require something called Methodology. But that's fine, my intention was not to argue, only to request that claims be addressed, or at least some type of response. My apologies.

[ruxtmp]

While Razbam actions speak behalf, it is for me more like that they were caught with the demand for quality. As somewhere did I read that razham said that they make a lot just by guessing, before they learn better. Why example Mirage got major changes to it as Ada approached and told what is wrong. And harrier got major changes as it was forum members who picked up details from NATOPS and videos and explained them to razbam.

 

So in my eyes it is more that razbam is learning that on what level to produce features, than coding itself. As you can be excellent programmer, but if you implement systems wrong or don't even know how they work, how could you do it right?

 

If RAZBAM did not have the appropriate information or understanding of how said systems worked then why in the world would they even have attempted to build a module like the Harrier? If this is truly the case I would be suspect of anything they push out. Other developers wont even touch an upgraded aircraft of one of their already created modules because they lack accurate information on some of its systems. Maybe RAZBAM should have released these modules as Flaming Cliffs versions, like the F-15C or A-10A, where the understanding is that the systems are lower fidelity or close approximations of the aircrafts systems and not a full representation of the aircraft.

[Hawkeye_UK]

Let not divert the OP's post and point which is about communication.

 

It is not negative or "trolling" in what i'm about to state. Razbam's communication with the community is disgusting when it comes to even acknowledging a fault in THEIR software, aka customers doing part of their job for them re testing for free and they cannot even be bothered to acknowledge the forum or discord or the person's effort to help their product. I cannot understand how they can be so far removed from reality they clearly lack a COO/CEO with any ability as the community manager would have been replaced along time ago if it was my company, plus i would have issued statements myself.

 

If you remember last summer there was a brewing resentment with ED along the longstanding players - what happened, they had to improve their communication. Yes there are lot of problems still, especially with the bugs but their communication has improved, because it had to. If you really want anything to happen then need to start putting pressure on ED to sort out one of their third party suppliers because they really do need the proverbial rocket firing up their rear ends. Its a job for Kate to pick up and deal with as Razbam are currently, and have been for some time an absolute shambles.

 

It makes me laugh when people start going on about the F15e or Mig23 - Are you seriously going to support a company that to all extents doesn't care about even the basics of communication. It's a point of principle.

 

I'm calling it early but i can feel another Hawk debacle coming on.....

[=DECOY=]

Hi guys,

 

We certainly do look at the forums however we haven't been as active for personel reasons however that will change now we are slowly getting back to normal, As a note our new testing team have been working hard looking at the latest reported bugs and will be adding to the tracker and passing to the coders accordingly. Soon I will introduce them on the Forums so you are aware who they are.

 

 

 

In relation to the existing modules the Coders have been very busy balancing the bugs across our modules to prevent the inevitable " your ignoring module x or y comments which always appear when we fix a certain module over another".

 

The speed of the fixes will hopefully pick up soon, we reviewed a lot of applications for our coder request and will be moving a few to the 2nd stage soon, so what this space..

 

 

 

 

 

Just in case you haven't seen the last months worth of BUG FIXES, please see below !

 

 

Fix IFR Probe responding to switch command without hydraulic power available

Fixed cockpit alerts (cautions, voice warnings, maneuver tone, RWR alerts, weapon tones) to properly go through headphone/headset source

Fixed incorrect RPM bias due to H2O mode working with Manual Fuel enabled

Fixed H2O dump not functioning

Fixed 2x Right MK-82 AIR incorrectly set as MK-82 Snakeyes

Fixed MK-81 positioning

Overhaul to WCA and Voice Warning logic for better management of fault acknowledgement and priority

Fixed 15 SEC solid vs. flashing logic

Further improved GPWS cues

Improved auto-start sequence to give more time for cues to be heard through sequence

Fixed DEP RES should only show when degraded not when in operation

Fixed SKID should cause CAUTION CAUTION when Anti-Skid is OFF

Fixed required time between BINGO auditory warning to be 60 seconds

Fixed required time between FUEL LOW LEFT or FUEL LOW RIGHT auditory warning to be 60 seconds

Fixed required time between GPWS CHECK GEAR auditory warning to be 8 seconds

Improved JPTL limiter check logic

Fixed WCA for SAAHS Pitch, Roll, Yaw light not properly indicated SAAHS is disabled when paddle switch pressed

Fixed WCA for LIDS when position disagrees with nominal position (either due to retract override switch or hydraulic failure)

Fix voltmeter always stuck at 27.5V - during checklist voltmeter should now change during checklist tests

Fixed logic for DROOP light to go out during full aileron deflection per checklists

GPWS "Pull Up" rules rework to make it less sensitive

TPOD now stows when placed in Standby

Sidewinder SEAM mode is enabled

Sidewinder firing when not in AA mode bug fix

Sidearm firing when not in AG mode bug fix

MPCD + HUD Night mode update

EMERG Page with Emergency procedures is enabled

Various WCA and Auditory Cue Corrections

Corrected issue causing infinite sound bug

Improved delays of auditory cues to when the fault occurs

Improved prioritization of auditory cues based on fault priority

Fixed GEAR WCA light and auditory cue logic

Fixed errant CAUTION, CAUTION auditory alert when starting mission

Further improvements to GPWS auditory tone logic as well as corrected rules for determining GPWS alert conditions

Fixed CAUTION, CAUTION not allowed to replay for a minimum of 5 seconds if already played

 

 

 

 

P.S - Stay on Topic :lol:

Edited June 9, 2020 by =DECOY=

[kirk7312]

Thanks for your replay.

I think most of players are fastrated by the recent two big bugs（LMAV and Tarawa takeoff position） after super carrier release. that make a lot of missions unplayable.

[=DECOY=]

Thanks for your replay.

I think most of players are fastrated by the recent two big bugs（LMAV and Tarawa takeoff position） after super carrier release. that make a lot of missions unplayable.

 

 

Sometimes its not our fault things break , but we are trying to fix them.

 

 

As a note the the Tarawa has been fixed a few times this year :) We do try to keep up with the constant changes but sometimes this are beyond our control :)

[Cornelius]

Thanks for your replay.

I think most of players are fastrated by the recent two big bugs（LMAV and Tarawa takeoff position） after super carrier release. that make a lot of missions unplayable.

 

No, I don't think so

[Fisu_MAD]

No, I don't think so

+1,

Decoy, your words sounds good, but we need a lot of love, tons of love for this plane. I hope you have in target the fantastic job made to recap all the bugs and their status, made by this comunity.

Edited June 10, 2020 by Fisu_MAD
missing Decoy

[Kappa]

Thanks for your replay.

I think most of players are fastrated by the recent two big bugs（LMAV and Tarawa takeoff position） after super carrier release. that make a lot of missions unplayable.

 

Here I am, a frustrated player! :joystick:

 

 

There is no doubt that some bugs are not caused by Razbam, however, many others are caused by them. Just note that with each update when the change log reports something about the harrier, new bugs appear ...

Do we want to talk about the CCIP mode that activates the DMT without giving way to go to any other page?

 

Easy to blame ED for "some problems" but the reality is that there is a lot of work to be done on the Harrier and Razbam has to do it.

[Beltza]

Sorry about my bad english.

Yesterday a new update of a lot modules and nothing for the Harrier which has serious issues: LMAV, Tarawa positions and the Flir and lights. And nothing changed in this update for the Harrier but yes for a lot of modules. I use the new mod of the L-61 Juan Carlos I Carrier. When the positions to respawn were broken, they last one day to solve this. ¡Only one day! But the Tarawa, nothing for weeks. Sorry, I'm a fan of Razbam products but I'm really disapointed.

Edited June 11, 2020 by Beltza

[eddyimac]

Sorry about my bad english.

Yesterday a new update of a lot modules and nothing for the Harrier which has serious issues: LMAV, Tarawa positions and the Flir and lights. And nothing changed in this update for the Harrier but yes for a lot of modules. I use the new mod of the L-61 Juan Carlos I Carrier. When the positions to respawn were broken, they lasta one day to solve this. ¡Only one day! But the Tarawa, nothing for weeks. Sorry, I'm a fan of Razbam products but I'm really disapointed.

 

 

You are right Sir!!!!:thumbup:

[Rhinozherous]

Hi guys,

 

We certainly do look at the forums however we haven't been as active for personel reasons

 

......and here the problem starts, FROM THE VIEW OF YOUR CUSTOMERS. We all know that RAZBAM is not the biggest team. You have two modules that are quite old, the M2000 and the Harrier. While the Mirage seams to get better now after a time the Harrier has lots of bugs (see community bug tracker). But you start pumping out new modules like the F15, the Falklands, F23......

 

This, in conjunction with personel problems + bugs in existing modules + very low communications has to lead to the impression that there is very low care for existing modules and customers.

[shagrat]

Sorry about my bad english.

Yesterday a new update of a lot modules and nothing for the Harrier which has serious issues: LMAV, Tarawa positions and the Flir and lights. And nothing changed in this update for the Harrier but yes for a lot of modules. I use the new mod of the L-61 Juan Carlos I Carrier. When the positions to respawn were broken, they last one day to solve this. ¡Only one day! But the Tarawa, nothing for weeks. Sorry, I'm a fan of Razbam products but I'm really disapointed.

so if there is one update, where they couldn't add any fixes, to stuff depending on the core environment (EDs responsibility), like the spawn L

logic for carriers, or the weapons API, you cry "murder"?

If you haven't noticed they were actually very busy the last months fixing issues and adding stuff:

https://www.digitalcombatsimulator.c...ews/changelog/

 

02.06.2020

DCS AV-8B by RAZBAM

 

Fix IFR Probe responding to switch command without hydraulic power available

 

Fixed cockpit alerts (cautions, voice warnings, maneuver tone, RWR alerts, weapon tones) to properly go through headphone/headset source

 

Fixed incorrect RPM bias due to H2O mode working with Manual Fuel enabled

 

Fixed H2O dump not functioning

 

Fixed 2x Right MK-82 AIR incorrectly set as MK-82 Snakeyes

 

Fixed MK-81 positioning

 

Overhaul to WCA and Voice Warning logic for better management of fault acknowledgement and priority

 

Fixed 15 SEC solid vs. flashing logic

 

Further improved GPWS cues

 

Improved auto-start sequence to give more time for cues to be heard through sequence

 

Fixed DEP RES should only show when degraded not when in operation

 

Fixed SKID should cause CAUTION CAUTION when Anti-Skid is OFF

 

Fixed required time between BINGO auditory warning to be 60 seconds

 

Fixed required time between FUEL LOW LEFT or FUEL LOW RIGHT auditory warning to be 60 seconds

 

Fixed required time between GPWS CHECK GEAR auditory warning to be 8 seconds

 

Improved JPTL limiter check logic

 

Fixed WCA for SAAHS Pitch, Roll, Yaw light not properly indicated SAAHS is disabled when paddle switch pressed

 

Fixed WCA for LIDS when position disagrees with nominal position (either due to retract override switch or hydraulic failure)

 

Fix voltmeter always stuck at 27.5V - during checklist voltmeter should now change during checklist tests

 

Fixed logic for DROOP light to go out during full aileron deflection per checklists

 

19.05.2020

DCS AV-8B by RAZBAM

 

GPWS "Pull Up" rules rework to make it less sensitive

 

TPOD now stows when placed in Standby

 

Sidewinder SEAM mode is enabled

 

Sidewinder firing when not in AA mode bug fix

 

Sidearm firing when not in AG mode bug fix

 

MPCD + HUD Night mode update

 

EMERG Page with Emergency procedures is enabled

 

 

Various WCA and Auditory Cue Corrections

 

Corrected issue causing infinite sound bug

 

Improved delays of auditory cues to when the fault occurs

 

Improved prioritization of auditory cues based on fault priority

 

Fixed GEAR WCA light and auditory cue logic

 

Fixed errant CAUTION, CAUTION auditory alert when starting mission

 

Further improvements to GPWS auditory tone logic as well as corrected rules for determining GPWS alert conditions

 

Fixed CAUTION, CAUTION not allowed to replay for a minimum of 5 seconds if already played

 

16.04.2020

DCS AV-8B by RAZBAM

 

Updated exterior models - fixed tail code number

 

Updated Training Mission 9 (LHA) - TACAN changed so there is no conflict with Kobuleti

 

03.03.2020

DCS AV-8B by RAZBAM

 

NSEQ routing now enabled

 

EHSD Overlay 1: Air refueling zones enabled (max 3)

 

EHSD Overlay 2: Flight plan route display enabled

 

ILV cockpit files updated

 

Fixed issue with the guns firing with a Nozzle angle less than 30 Degrees

 

Fixed fuel pump keybind issue

 

Improved nose wheel steering logic

 

20.02.2020

DCS AV-8B by RAZBAM

 

Fixed issue with invisible KC-130 Tanker

 

13.02.2020

DCS AV-8B by RAZBAM

 

CAS page update, you can now edit and delete records

 

Fixed cockpit texture text issue

 

Fixed bomb release order

 

Fixed CTD after alignment when selecting DATA page

 

Fixed Flashing letters in HUD

 

Fixed TACAN offset symbol position in the MPCD

 

Fixed VVM HUD position will now remain on the same horizontal plane with the GVM

 

Changed the gun pod ammo to PGU-32/U SAPHEI-T 25 mm rounds

[Kappa]

so if there is one update, where they couldn't add any fixes, to stuff depending on the core environment (EDs responsibility), like the spawn L

logic for carriers, or the weapons API, you cry "murder"?

If you haven't noticed they were actually very busy the last months fixing issues and adding stuff:

https://www.digitalcombatsimulator.c...ews/changelog/

 

02.06.2020

DCS AV-8B by RAZBAM

 

Fix IFR Probe responding to switch command without hydraulic power available

 

Fixed cockpit alerts (cautions, voice warnings, maneuver tone, RWR alerts, weapon tones) to properly go through headphone/headset source

 

Fixed incorrect RPM bias due to H2O mode working with Manual Fuel enabled

 

Fixed H2O dump not functioning

 

Fixed 2x Right MK-82 AIR incorrectly set as MK-82 Snakeyes

 

Fixed MK-81 positioning

 

Overhaul to WCA and Voice Warning logic for better management of fault acknowledgement and priority

 

Fixed 15 SEC solid vs. flashing logic

 

Further improved GPWS cues

 

Improved auto-start sequence to give more time for cues to be heard through sequence

 

Fixed DEP RES should only show when degraded not when in operation

 

Fixed SKID should cause CAUTION CAUTION when Anti-Skid is OFF

 

Fixed required time between BINGO auditory warning to be 60 seconds

 

Fixed required time between FUEL LOW LEFT or FUEL LOW RIGHT auditory warning to be 60 seconds

 

Fixed required time between GPWS CHECK GEAR auditory warning to be 8 seconds

 

Improved JPTL limiter check logic

 

Fixed WCA for SAAHS Pitch, Roll, Yaw light not properly indicated SAAHS is disabled when paddle switch pressed

 

Fixed WCA for LIDS when position disagrees with nominal position (either due to retract override switch or hydraulic failure)

 

Fix voltmeter always stuck at 27.5V - during checklist voltmeter should now change during checklist tests

 

Fixed logic for DROOP light to go out during full aileron deflection per checklists

 

19.05.2020

DCS AV-8B by RAZBAM

 

GPWS "Pull Up" rules rework to make it less sensitive

 

TPOD now stows when placed in Standby

 

Sidewinder SEAM mode is enabled

 

Sidewinder firing when not in AA mode bug fix

 

Sidearm firing when not in AG mode bug fix

 

MPCD + HUD Night mode update

 

EMERG Page with Emergency procedures is enabled

 

 

Various WCA and Auditory Cue Corrections

 

Corrected issue causing infinite sound bug

 

Improved delays of auditory cues to when the fault occurs

 

Improved prioritization of auditory cues based on fault priority

 

Fixed GEAR WCA light and auditory cue logic

 

Fixed errant CAUTION, CAUTION auditory alert when starting mission

 

Further improvements to GPWS auditory tone logic as well as corrected rules for determining GPWS alert conditions

 

Fixed CAUTION, CAUTION not allowed to replay for a minimum of 5 seconds if already played

 

16.04.2020

DCS AV-8B by RAZBAM

 

Updated exterior models - fixed tail code number

 

Updated Training Mission 9 (LHA) - TACAN changed so there is no conflict with Kobuleti

 

03.03.2020

DCS AV-8B by RAZBAM

 

NSEQ routing now enabled

 

EHSD Overlay 1: Air refueling zones enabled (max 3)

 

EHSD Overlay 2: Flight plan route display enabled

 

ILV cockpit files updated

 

Fixed issue with the guns firing with a Nozzle angle less than 30 Degrees

 

Fixed fuel pump keybind issue

 

Improved nose wheel steering logic

 

20.02.2020

DCS AV-8B by RAZBAM

 

Fixed issue with invisible KC-130 Tanker

 

13.02.2020

DCS AV-8B by RAZBAM

 

CAS page update, you can now edit and delete records

 

Fixed cockpit texture text issue

 

Fixed bomb release order

 

Fixed CTD after alignment when selecting DATA page

 

Fixed Flashing letters in HUD

 

Fixed TACAN offset symbol position in the MPCD

 

Fixed VVM HUD position will now remain on the same horizontal plane with the GVM

 

Changed the gun pod ammo to PGU-32/U SAPHEI-T 25 mm rounds

 

Dude... 1 update per month... A lot of minor bug fixes that have also caused more bugs...

 

C'mon, you can't be seriuos... look at other modules change logs...

Edited June 11, 2020 by Kappa

[shagrat]

Dude... 1 update per month... A lot of minor bug fixes that have also caused more bugs...

 

C'mon, you can't be seriuos... look at other modules change logs...

I am pretty serious. If you compare the changelogs to "other modules" you should compare it to modules in a similar state of development, like the MiG-21, Viggen, Yak-52. The ones with "major updates" are the ones, in basic development, with lots of missing features added each update and less bugfixes.

What Razbam needs to take responsibility for, is the tremendous timespan it took them to get to this state. Yes, they were reorganizing, yes, they had a deep look into the real Mirage and took time to get subject matter experts feedback on the AV-8B and it really took much too long for my liking, but they did go through that change and it seems, they now constantly fix bugs, actively develop the last system details and hopefully are back on track.

As Decoy said, they try to balance fixing the Harrier and Mirage, so they don't get yet another shitstorm because they "abandon" one or the other, but I am very happy, we see a lot of things being worked on and especially long standing issues like the Audio adressed etc.

The last OpenBeta update(s) caused a lot of issues not only for the AV-8B and it is partly related to the overhaul of parts of the core engine. So not necessarily something Razbam can easily fix on their own, if at all.

In some cases it is even a bad idea to try to fix things while they are still in development by ED (new lighting, Carrier AI and Logic), just saying.

 

P.S. and btw the update cycle is managed by ED, as well as the build process for updates. 3rd parties simply can't provide more than the sources for the build process so they hopefully make it into the next update, which are "planned" every two weeks, unless ED pushes a hotfix...

Edited June 11, 2020 by shagrat

[Beltza]

so if there is one update, where they couldn't add any fixes, to stuff depending on the core environment (EDs responsibility), like the spawn L

logic for carriers, or the weapons API, you cry "murder"?

If you haven't noticed they were actually very busy the last months fixing issues and adding stuff:

https://www.digitalcombatsimulator.c...ews/changelog/

 

So, do you mean we have to be quiet?

Sorry, but no. I understand that RAZBAM is not involved in everything related to the simulator problems. But as players and customers of RAZBAM we must ask for the errors to be corrected, errors that remain for months, and if RAZBAM cannot solve them, it is they who should ask ED to fix them. But with our silence, that chain brokes.

It is not a question of asking for the "murder" of anyone, but of pressing for these errors to be corrected. We have paid for the modules, therefore we have the right to behave as clients and if the requests are made correctly and politely there should be no problem.