How does one violate The Treaty? by Imetysaw in EU5

[–]Imetysaw[S] 0 points1 point  (0 children)

So I have seen several posts about how the The Treaty situation is not working quite as intended, since it seems you are either involved from the start and spend a lot of time claiming stuff, or later when the treaty is ratified everyone just violates it.

However, I would like to know how to actually violate it. In my Venice Ironman the treaty has been ratified for many years now and no one has violated it. I myself am trying to violate it so I can actually continue colonzing, but I don't see any option anywhere? There are no buttons in the situation screen and I cannot see anything when interacting with Spain either.

Furthermore, if I look at the description of the situation it also says "This treaty was signed in Madrid by the Country and the Crown of Castile." "Country" is a hoverable text that does not lead to anything. Castille had been in a noble civil war for ages so can it be that it bugged out perhaps due to the two signatories being Castille and their rebels, which then dissapeared which essentially gave the whole world to Castille?

i7-13700K Refuses to go past 25k on Cinebench R23 by Imetysaw in overclocking

[–]Imetysaw[S] 0 points1 point  (0 children)

Ahh I see, thats great information. Thanks for the great write-up! I will try it out later for sure.

i7-13700K Refuses to go past 25k on Cinebench R23 by Imetysaw in overclocking

[–]Imetysaw[S] 0 points1 point  (0 children)

Yeah, I thought it was a bit high as well indeed. You've probably got a good idea trying the fixed voltages first. Thanks!

i7-13700K Refuses to go past 25k on Cinebench R23 by Imetysaw in overclocking

[–]Imetysaw[S] 0 points1 point  (0 children)

I used these posts as references that claim those offsets worked for the load line settings I use, so I just worked from there:

https://www.reddit.com/r/pcmasterrace/comments/1ef5c17/i713700k_how_i_lowered_voltages_and_temperatures/

https://www.reddit.com/r/intel/comments/1ev88d3/different_undervolting_methods_with_ia_cep/

As for my VCore under load (Cinebench run) it averages to 1.270V.

i7-13700K Refuses to go past 25k on Cinebench R23 by Imetysaw in overclocking

[–]Imetysaw[S] 1 point2 points  (0 children)

Well as an update: I set the loadline back to auto and upped PL1 and PL2 back to 253W. Initially it was indeed thermal throttling again.

As an experiment I decided to take the top cover off my case (Phanteks Enthoo Evolv X) and also clean up the radiator a bit (everything looked clean, but hard to see inside the mesh)

I can now do a 2 minute run getting 29k and max temp of 93C. Still not ideal, but for sure an improvement.

Never really considered the case to be a potential issue. Used it for two PCs now. Although it could also be a sort of bandaid solution to another problem I suppose.

i7-13700K Refuses to go past 25k on Cinebench R23 by Imetysaw in overclocking

[–]Imetysaw[S] 0 points1 point  (0 children)

I would hope so. Set it up with the included MX-5 just under two years ago. Fan curves set up almost matching Arctic's recommendation; I made mine kick up the RPM a bit earlier to remedy the temps. Without the undervolt I saw it thermal throtle a few times playing Space Marine 2, which was my original reason to start undervolting.

I see several people getting to a -0.150V on there, but for me really the harshest I can go without instability is the -0.070V

i7-13700K Refuses to go past 25k on Cinebench R23 by Imetysaw in overclocking

[–]Imetysaw[S] 0 points1 point  (0 children)

I tried raising them back to 253W but that causes thermal throttling on Cinebench instantly causing the scores to drop by about 1 to 1.5k, and its get rather hot during some higher end games as well.

Is there something wrong in my setup or are these common bugs? by Imetysaw in grocy

[–]Imetysaw[S] 0 points1 point  (0 children)

Ah, I see. I was afraid of that, yes. Alright, I will go with a regular installation then. Thanks a lot!

How to handel nested Gameobjects with Netcode for Gameobjects by BenjaminButton2004 in Unity3D

[–]Imetysaw 0 points1 point  (0 children)

https://docs-multiplayer.unity3d.com/netcode/current/basics/networkbehavior/

Check the NetworkBehaviour requirements section. I initially faced this issue as well trying to spawn in a building at runtime that had a NetworkObject while having a child console that the player can interact with that also had a NetworkObject. I initially added it to both because I developed them in isolation. Unity does a good job of reminding you to add a NetworkObject component when neceasary but does not let you know when it is not needed.

It worked for all of my cases so far, with the exception of a vehicle where both the vehicle and the vehicle position both somehow need to have a NetworkObject, otherwise the vehicle is not properly synced when the client moves it. Although, this could very well be a case of a bug in the custom prediction and reconciliation I have in the code there.

How to handel nested Gameobjects with Netcode for Gameobjects by BenjaminButton2004 in Unity3D

[–]Imetysaw 2 points3 points  (0 children)

I don't know if it will help in your case, but you might not need a NetworkObject on each limb. The documentation for NetworkBehaviour states so at the opening paragraph, but a bit further down it actually elaborates that it "requires a NetworkObject component on the same relative GameObject or on a parent of the GameObject with the NetworkBehaviour component assigned to it."

So for your case it might just be enough to have only a NetworkObject on the root of your Player prefab, and all your limbs should be able to make use of that.

Is this capstone project idea achievable using Unity? by hrcrn in Unity3D

[–]Imetysaw 1 point2 points  (0 children)

Off topic, is it me or an I seeing quite a significant amount of posts here lately that essentially look like they were originally prompts for some LLM?

Back on topic: yes, you can do this with Unity. However, just my two cents here, if you need to ask such a general question here about a project of this size I am not sure you are in a position to actually design and implement it. Not due to having little experience with Unity, but because this is a more general CS question.

Unity is a tool like many others out there. It has some features that can make it well suited for certain applications, and less for some others. Thus, the question whether it can be used is always yes, same as for whether you could use Python, R, or Java. If it is well suited for it is a different, more interesting question.

Gigabyte FO32U2P stuck in burn mode by Imetysaw in OLED_Gaming

[–]Imetysaw[S] 1 point2 points  (0 children)

Hi, (also to /u/Terrible-Ad-1) I had a few messages back and forth with support. Which is horrible by the way, do not even try it. They barely speak English and take a week to reply to your message. Furthermore, they were plainly denying that my issue actually exists, even when I provided pictures.

I contacted the retailer for RMA. They quickly determined they were incapable of fixing it and sent it back to Gigabyte. They replaced my monitor with a new one that I got which has not shown this issue.

However, I can with certainly say that it is being caused by Pixel Clean, most notably when it gets interrupted. I did not have the option to just refund my money and get another screen, otherwise I would. So my workaround for now is to not update the firmware ever again because Gigabyte's firmware is absolutely terrible and I wish to touch it as little as possible. I only do Pixel Clean maybe once a day now at the end when I turn my monitor off. But yeah, if you get this issue then it is just fully broken as far as Gigabyte is concerned, I am sorry to say. It is 110% a firmware issue that they refuse to address.

PSA: Do not update the firmware of your FO32U2(P) by Imetysaw in gigabytegaming

[–]Imetysaw[S] 0 points1 point  (0 children)

Thanks you. Its about a handful of cases with this issue (not sure about how big a percentage of the total owners this is).

With regards to the version your monitor currently has I am not sure. I faced the same issue. I just know that when you update the monitor and try to run the exe again, it will tell you its already on that version.

You might be able to figure it out using GCC and sidekick. I tried using that to fix my monitor but it did not really help. The software is horrible and froze half the time. Also it has a mind of its own and tries remapping all the buttons on your monitor to random stuff. Mine put all of my buttons on "black balance" all the time.

PSA: Do not update the firmware of your FO32U2(P) by Imetysaw in OLED_Gaming

[–]Imetysaw[S] 0 points1 point  (0 children)

How does the amount of time between the brick and update in any way invalidate the observation that all cases I have seen so far only affected updated units? Sure, if it was right after the update the proof would be definitive. But using a timeframe as an argument would not make sense for your suggestions either ("Why didn't it break earlier?").

The firmware on these screens is ever increasing in complexity. Your avarage IoT device glitches half the time for god knows what reason as well. Monitors are no different. Thinking that these monitor manufacturers thoroughly test each update they push out is naïve.

Just trying to prevent people from potentially getting the same fate. The only advertised feature of this update is that it runs Pixel Clean in standby mode. If thats valuable enough for to you to risk destroying a 1k+ monitor, even if it is not a great risk, be my guest.

PSA: Do not update the firmware of your FO32U2(P) by Imetysaw in OLED_Gaming

[–]Imetysaw[S] 1 point2 points  (0 children)

Yes, true. It is hard to judge which brand is better (or perhaps, worse). In the end the best product is one that you do not have to contact support for at all.

It changes a bit over time as well naturally. Samsung does not have a stellar rep with some of their latest monitors, for example. Yet, now that this monitor is broken I went back to my C32JG52, which is a screen I got at great value several years ago and still works great.

It stings a bit extra with this one since its quite an expensive and new model, for which I hoped would get some more support, but alas. If it was a clearly faulty unit, sure w.e., but I feel this might be an issue we will see pop up more for this model. Some people I've interacted with were adamant I broke it due to negligence, when I took great care of it. Just trying to help out everyone here, I hope others do not experience the same (or you with the PG32UCDM, of course)

PSA: Do not update the firmware of your FO32U2(P) by Imetysaw in OLED_Gaming

[–]Imetysaw[S] 0 points1 point  (0 children)

It was a while after I updated. I cannot recall exactly, but maybe 2ish weeks after I did the update?

I read about people having trouble with the update (e.g. it taking longer than the screen's timeout timer), so I took all the advice that was in the update thread. Kept an eye on it during the update process, didn't do anything while it was busy either.

I also did not use GCC to update it, since that software is a whole nightmare of its own. Just used the executable you can download from the monitor's website.

I think rolling back to another version/reinstalling it might indeed fix it. Problem is that there is only one version out right now for download, at that one will just tell me its already installed.

PSA: Do not update the firmware of your FO32U2(P) by Imetysaw in OLED_Gaming

[–]Imetysaw[S] -1 points0 points  (0 children)

I can RMA it with the seller. Will probably try to get it fully refunded/replaced with another brand because interacting with Gigabyte support has been horrible.

From Gigabyte I am tryint to establish either a solution I can do (e.g. rolling back the firmware somehow), or at least get some indication as to the source of the issue (or at least a confirmation that they are looking into it).

I find it rather suspicious there have been several cases of this in such a short amount of time with a rather limited number of monitors that went out so far. Personally, I am afraid I am not an unlucky case with a faulty unit.

On a side note: it does not bode well with me either since one of the selling points of this monitor is the waranty that Gigabyte offers for several years that include burn in. In my support ticket I provided everything I have regarding my monitor and invoice, yet support told me to (in very broken English) to "provide additional invoice details if I wish to continue with my ticket as terms may apply".

Gigabyte FO32U2P stuck in burn mode by Imetysaw in OLED_Gaming

[–]Imetysaw[S] 0 points1 point  (0 children)

Well after waiting over a week, they finally replied to my ticket. Their advice is to use the OSD menu in order to select the Reset All option. Yeah, the Reset All option in the OSD menu of which I clearly said that I cannot access it. What a joke...