PC v1.x Developer Diary

Status
Not open for further replies.
If you're discussing bugs but not submitting them, there is a very good chance they won't be seen here.  It makes little to no sense to post them in this thread.  Just look at how many pages this thread is and how quickly we move to a new page.  Do you think a bug posted about here is likely to be noticed by the devs?  They aren't likely to spend a ton of time browsing the forum and certainly aren't looking at this thread to find bugs.  There is a very good reason that they should be posted to the location where bugs are supposed to be posted so the devs can see them.  Other discussions, which most of this thread has (only a very small number of posts out of 200+ pages are about bugs) are fine.  If we can get 200+ pages of discussion where 99% isn't about bugs, I'd say we have plenty to talk about.

And faatal already agreed that it was about time to start putting together a 2.0 dev diary, so be patient and we might see something soon since he said that.

 
The only one doing anything is faatal on his own volition, and we're grateful for that, but what is the purpose of a dev diary with no content or regular updates provided by the devs themselves?
Thats how i see it to, The whole reason i really even started posting on this forum last month is because i felt faatal is really the last main hope to get any major bugs fixed that alot of people been asking for so, i much rather see him work on those than new content i guess, just being honest.

 
Then ask TFP to release some friggin' content update regularly on this "Dev Diary". The only one doing anything is faatal on his own volition, and we're grateful for that, but what is the purpose of a dev diary with no content or regular updates provided by the devs themselves?

It's all speculating and lamenting after a while, if there's no dev interaction people will start to eat their nails and spit on each other ffs

I'm fully supportive of the devs, believe me, but you can't blame people for derailing when there's almost nothing to be derailed in the first place.


Pretty much this. Aside from Faatal, who is understandably busy, the Fun Pimps are notoriously horrible at communication.

 
 If Nvidia made it available to be used by AMD and older Nvidia cards, there would be more interest in developing for it.  Right or wrong, that's just how things work.


Nvidia did make Streamline which is sort of an open source API for adding any SR solution. AMD decided not to support it, while Intel did. Which it has become part of the DirectSR(DX12) API. So in theory, it should be easier for DLSS, FSR and XeSS to be implemented in to a game with DirectSR.

The main point of my post was "But PLEASE don't gut the underlying code/framework that Laydor used to get the DLSS mod working."
So long as they keep the Nvidia Unity Plugin module stuff and nvngx_dlss.dll, the mod should work fine without any additional work.

 
The bug pool should be migrated to the main forum, right under the General Support forum - "POST BUGS HERE". Nice and easy. Blatant and obvious.

Right now you gotta click the banner. Then you got to sift through a big post. Then you gotta click something else which brings you somewhere that isn't exactly laid out like the rest of the forum. Regardless if it's not truly difficult to navigate, the way it's set up now is a deterrent. That is why people post bugs here.
If it is your first time, then you HAVE TO READ THE INSTRUCTIONS so there are no people reporting random stuff of making incomplete reports that wouldn't be helpful anyways.
If it's not your first time, then you already know what to do and the report is just 2 - 3 clicks away. no big deal.
Reporting bugs here does absolutely nothing since they will get just washed away and not be tracked at all.
Being lazy and not wanting to read the instructions once to do things properly is no excuse to hijack other channels.

 
I totally understand that they stated cr is for dev use, that basically means now they expect server owners to wipe all players bases in the region just to fix a small prefab or chunk in an area. That honelty to me doesn't make sense nor would it be fair to any player who gets their base wiped over a small chunk issue. Seriously, any reasonable admin would probably agree.

View attachment 33495
Sounds like you don't know how to use the DEV tools in-game to clear a player base, and just want a simple command to do your work. A few minutes with the DEV Super Digger and the Dev Terrain Modeling tool make quick work of removing a players base. That's part of the work of running a server.

 
If it is your first time, then you HAVE TO READ THE INSTRUCTIONS so there are no people reporting random stuff of making incomplete reports that wouldn't be helpful anyways.
If it's not your first time, then you already know what to do and the report is just 2 - 3 clicks away. no big deal.
Reporting bugs here does absolutely nothing since they will get just washed away and not be tracked at all.
Being lazy and not wanting to read the instructions once to do things properly is no excuse to hijack other channels.
That's great but people don't work like that. The vast majority of people are not going to want to do something unless it's made as easy as possible. Think about it from a business perspective. If you create a product but not make it super easy to obtain, you're not going to have a lot of sales. So you can either make it easy for the customers, or you can complain that they're too lazy while you're filing for bankruptcy. 

 
That's great but people don't work like that. The vast majority of people are not going to want to do something unless it's made as easy as possible. Think about it from a business perspective. If you create a product but not make it super easy to obtain, you're not going to have a lot of sales. So you can either make it easy for the customers, or you can complain that they're too lazy while you're filing for bankruptcy. 


Personally, I think it should be fine for people to still have to formally file a bug report...it helps run down the problem. That said...it should also be fine for people to discuss bugs here as well. 

 
Sounds like you don't know how to use the DEV tools in-game to clear a player base, and just want a simple command to do your work. A few minutes with the DEV Super Digger and the Dev Terrain Modeling tool make quick work of removing a players base. That's part of the work of running a server.
what exactly does using dev tools have to do when regions get fully reset?

That post i made was to show the results of what  could happen when a region gets reset... so yeah i believe any admin would agree its not worth resetting all the bases of players in a reagion over a small chunk issue, Thats why cr was so important for admins to have...... it prevented such things.

 
what exactly does using dev tools have to do when regions get fully reset?

That post i made was to show the results of what  could happen when a region gets reset... so yeah i believe any admin would agree its not worth resetting all the bases of players in a reagion over a small chunk issue, Thats why cr was so important for admins to have...... it prevented such things.
You were talking about CR Chunk Reset... with no Chunk Reset and not resetting the Region File you have to clear the playerbase using the DEV tools etc..

 
You were talking about CR Chunk Reset... with no Chunk Reset and not resetting the Region File you have to clear the playerbase using the DEV tools etc..
umm, no

not even close..

what i was talking about if a region gets reset it resets everything in that region..

Honestly dont really know how to state it more simpler than that.

 
That's great but people don't work like that. The vast majority of people are not going to want to do something unless it's made as easy as possible. Think about it from a business perspective. If you create a product but not make it super easy to obtain, you're not going to have a lot of sales. So you can either make it easy for the customers, or you can complain that they're too lazy while you're filing for bankruptcy. 


Personally, I think it should be fine for people to still have to formally file a bug report...it helps run down the problem. That said...it should also be fine for people to discuss bugs here as well. 


I am not really a fan of the bug system they use here or how it's set up.  However, it does weed out a lot of reports that aren't useful, so I can't really fault them for it.  Yes, many people will not bother reporting a bug because they don't want to deal with it, but if it's a bug that affects more than that one person, someone will end up reporting it.  There are better options, but this is what they are using.  We have two choices - report bugs or don't.  If it is really so horrible that you would rather a bug not get fixed than to spend a few minutes reporting it the way they want, then just don't report the bug.

As far as discussion goes, the General Support forum is a far better place for that than the dev diary thread.  And devs do sometimes pick up on bugs that are posted there, which doesn't happen too often here.  So it at least has some value there, unlike posting here.  In any case, the mods have said not to discuss the bugs here, so that's really an end to it.

 
@Grandpa Minion

I think i might kinda sorta understand. What you are talking about is if you manually use region reset now its the same as just deleting
a region in solo play all goes poof. What you want to do is leave the player bases alone and reset poi's that have been scavenged already,
to reset resources. Is that close?

An alternative that may be possible and already has the base code, but I have no clue how much would have to be changed is. "the quest system
poi reset" There seems to be a designation, or identifier for those pois to be reset after use, i guess similar to chunk reset because it doesn't touch
anything else.

What if the LCB which designates an area as a  playerbase, which is in use already, had a similar identifier added to it. So when you do a manual
server region reset it is actually resetting all chunks that do not have that identifier. Sort of how you use a mask in a TGA or PNG file. A map is made,

as pois are created, a common is given to make a reset mask. Any lcb perimeter area is blocked out an all other areas are reset. That plus the

automated region reset should cover what you need, at least for now.

Again I don't know how much would need to changed, or if it would be considered.

Does the automated region reset, already skip player areas"  If so then would it not be easier to just run the command and reset the entire area.

If it does not skip player area then the above may be an option. From my view if I were an admin, I'd rather press one button and reset all incidental

area at once.

 
Last edited by a moderator:
I am not really a fan of the bug system they use here or how it's set up.  However, it does weed out a lot of reports that aren't useful, so I can't really fault them for it.  Yes, many people will not bother reporting a bug because they don't want to deal with it, but if it's a bug that affects more than that one person, someone will end up reporting it.  There are better options, but this is what they are using.  We have two choices - report bugs or don't.  If it is really so horrible that you would rather a bug not get fixed than to spend a few minutes reporting it the way they want, then just don't report the bug.

As far as discussion goes, the General Support forum is a far better place for that than the dev diary thread.  And devs do sometimes pick up on bugs that are posted there, which doesn't happen too often here.  So it at least has some value there, unlike posting here.  In any case, the mods have said not to discuss the bugs here, so that's really an end to it.


I think what people were/are asking for is the space to @%$# about the bugs. I could be wrong about that, but, that was the impression I was getting from the conversation. You are right that THIS space is the wrong one(especially after the mods said so)...having no place for those conversations seems wrong. Perhaps a separate tab or a subsection under bug reporting. It's just a thought.

 
@Grandpa Minion

I think i might kinda sorta understand. What you are talking about is if you manually use region reset now its the same as just deleting
a region in solo play all goes poof. What you want to do is leave the player bases alone and reset poi's that have been scavenged already,
to reset resources. Is that close?
Thats only a part of the issue, i dont want to have to reset everyones bases because a small chunk needs repaired whether it be a prefab or map corruption, and yeah alot of players dont use lcbs in multiplayer due to the sonar base finding exploit in them. Before with cr we could just reset the small area that needed it but now they are wanting us to reset whole regions instead to fix a small problem, to me that doesn't make sense.

 
What if the LCB which designates an area as a  playerbase, which is in use already, had a similar identifier added to it. So when you do a manual
server region reset it is actually resetting all chunks that do not have that identifier. Sort of how you use a mask in a TGA or PNG file. A map is made,

as pois are created, a common is given to make a reset mask. Any lcb perimeter area is blocked out an all other areas are reset. That plus the

automated region reset should cover what you need, at least for now.
It already works that way.  Region Reset will not affect an area that is protected with an LCB.  But Grandpa Minion does PVP and they don't like using LCBs because of that, so nothing is protected.

I think what people were/are asking for is the space to @%$# about the bugs. I could be wrong about that, but, that was the impression I was getting from the conversation. You are right that THIS space is the wrong one(especially after the mods said so)...having no place for those conversations seems wrong. Perhaps a separate tab or a subsection under bug reporting. It's just a thought.
People discuss bugs frequently in the General Support forum.  Now, obviously they want you to actually report the bugs in the right place, but I personally think it's fine to discuss them in the support forum.  Of course, I'm not a moderator and they may disagree.  But there is a lot of discussion there.  And I've seen devs and QA comment on stuff that's posted there and even add a bug report themselves, so they do see stuff there, which they probably don't here.

That being said, that forum is more about support.  If it's just discussing bugs that are known bugs, then General Discussion might be the best place to just talk about them since it's general discussion.  If you're not looking for support and the bugs are known bugs that don't need to be reported, then General Discussion probably makes the most sense.

 
Here’s how I’d put it. General Support is for ‘I’m having a problem with the (vanilla) game; someone please help me troubleshoot it, with the goal of getting my game working.’ The Bug Pool is for ‘I think there’s a reproducible error with the game itself, not to do with anything on my end. I want QA to know about it.’

In some cases, it may not be clear whether the issue you’re experiencing is one or the other, especially for less tech savvy users. That’s okay. People watching both spaces are generally understanding about that. They’d rather have you post in either space, since people ultimately want to help where they can.

This thread, however, is not a space for either type of issue. The dev diary is for the developers - those that choose to - to share about what they’re working on for future builds, and people’s reactions to and discussion around that.

There will be times when there’s not enough news to keep people entertained. The dev diary gets a lot of latitude during these times, but it doesn’t mean it’s time to fill the vacuum by bringing in subjects that are better covered on other parts of the forum.

...it will be done when its done...


This is true. We all must accept that the devs will share more when they are ready. I see zero chance they’d release e.g. Storms Brewing on people without talking a lot about it first. :)

 
Status
Not open for further replies.
Back
Top