Developer Assistant so bad

I constantly see that the “developer assistant” provides obviously incorrect and non-working functions. For the simplest questions, he gives obviously complex and non-working implementations. For example, to limit the FPS of a player in the Shipping assembly on blueprint, he says that you need to create c++
UFUNCTION(BlueprintCallable, Category=“Performance”)
static void SetFrameRateLimit(float FrameRateLimit);

He says initially you can’t do this from Blieprint, although there is a Set Frame Rate Limit function

The initial request was to create an FPS limit for players. The AI ​​suggests implementing this with a console command, which won’t work in the Shipping build. And he says that there is no other way to implement it.

This is just a small part of the horror they’re proposing.

The above is just an example; every request on any topic is accompanied by a questionable implementation from the AI ​​assistant.

On all issues he only confuses and complicates the solution.

We all understand that you need to think for yourself, but when you propose an assistant, it shouldn’t provide a knowingly incorrect and non-functional solution.

I’m sure the developers are long overdue for an update and retraining of the assistant. This doesn’t even look like a Beta version.

The above is written with the hope of improving the assistant :cry:

@Tina_Wisdom @SupportiveEntity

Hey there @qO_Op! Thanks for the feedback on the AI assistant. Hallucinations are a frustrating part of working with any LLM. I know this doesn’t correct the issue in the meantime, but whenever you come across an unhelpful response, thumbs down it so this can reinforce the LLM and help it gather better answers in the future.